ORA-01092 ORA-12432: LBAC error: zllegnp:OCIStmtExecute 故障一例-Mysql Tutorial-php.cn

Home

Database

Mysql Tutorial

ORA-01092 ORA-12432: LBAC error: zllegnp:OCIStmtExecute 故障一例

WBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWB

Jun 07, 2016 pm 05:31 PM

最近由于数据库hang住，无奈之下直接干掉了pmon进程，再次启动的时候收到了ORA-01092: ORACLE instance terminated. Disconnecti

最近由于数据库hang住，无奈之下直接干掉了pmon进程，再次启动的时候收到了ORA-01092: Oracle instance terminated. Disconnection forced以及ORA-12432: LBAC error: zllegnp:OCIStmtExecute。这下好了，有的整了，是个从来没有遇见的错误。下面是对这个错误的描述与解决。

1、故障描述
idle> startup
ORACLE instance started.

Total System Global Area 238530560 bytes
Fixed Size 1335724 bytes
Variable Size 167775828 bytes
Database Buffers 62914560 bytes
Redo Buffers 6504448 bytes
Database mounted.
ORA-01092: ORACLE instance terminated. Disconnection forced
ORA-12432: LBAC error: zllegnp:OCIStmtExecute
Process ID: 10704
Session ID: 125 Serial number: 5

2、故障分析
--首先看看提示的几个ORA说什么
[oracle@linux1 ~]$ oerr ora 1092
01092, 00000, "ORACLE instance terminated. Disconnection forced"
// *Cause: The instance this process was connected to was terminated
// abnormally, probably via a shutdown abort. This process
// was forced to disconnect from the instance.
// *Action: Examine the alert log for more details. When the instance has been
// restarted, retry action.
--上面的 ora 1092通常由于shutdown abort导致，需要查看alert日志

[oracle@linux1 ~]$ oerr ora 12432
12432, 00000, "LBAC error: %s"
// *Cause: LBAC enforcement resulted in an error.
// *Action: Correct the problem identified in the error message.
--上面ora 12432是关于LBAC的错误

--下面查看alert日志及其产生的trace文件
$ tail -fn 50 /u02/database/usbo/diag/rdbms/usbo/usbo/trace/alert_usbo.log
Tue Sep 03 14:58:39 2013
ARC3 started with pid=29, OS id=10716
SMON: enabling cache recovery
Archived Log entry 53 added for thread 1 sequence 57 ID 0xcde7041e dest 1:
Successfully onlined Undo Tablespace 2.
Verifying file header compatibility for 11g tablespace encryption..
Verifying 11g file header compatibility for tablespace encryption completed
SMON: enabling tx recovery
Database Characterset is AL32UTF8
No Resource Manager plan active
Errors in file /u02/database/usbo/diag/rdbms/usbo/usbo/trace/usbo_ora_10704.trc:
ORA-12432: LBAC error: zllegnp:OCIStmtExecute
Errors in file /u02/database/usbo/diag/rdbms/usbo/usbo/trace/usbo_ora_10704.trc:
ORA-12432: LBAC error: zllegnp:OCIStmtExecute
Error 12432 happened during db open, shutting down database
USER (ospid: 10704): terminating the instance due to error 12432
Instance terminated by USER, pid = 10704
ORA-1092 signalled during: ALTER DATABASE OPEN...
opiodr aborting process unknown ospid (10704) as a result of ORA-1092
Tue Sep 03 14:58:40 2013
ORA-1092 : opitsk aborting process

$ tail -10 /u02/database/usbo/diag/rdbms/usbo/usbo/trace/usbo_ora_10704.trc
Avg compares per lookup = 173/173 = 1.0
----------------------------------------------
Recovery sets nab of thread 1 seq 57 to 72 with 8 zeroblks

*** 2013-09-03 14:58:39.830
ORA-12432: LBAC error: zllegnp:OCIStmtExecute
ORA-12432: LBAC error: zllegnp:OCIStmtExecute

*** 2013-09-03 14:58:39.830
USER (ospid: 10704): terminating the instance due to error 12432
--上面的这些信息比较笼统，有些不好确认，查询metalink，，找到了解决方案
--ORA-01092 ORA-12432 LBAC ERROR ZLLEGNP While Starting Up An Instance (Doc ID 735801.1)
--尽管其版本范围是Oracle Database - Enterprise Edition - Version 11.1.0.6 to 11.1.0.6 [Release 11.1]，我的11.2版本依旧适用
--Oracle给出的无法启动的原因
The issue happens because the OLS metadata is incomplete as a result of a shutdown abort executed while the script catnools.sql (or catols.sql) was running.

3、故障解决
--Oracle给出的解决方案
--To solve this situation the LBAC option has to be disabled:
Step 1
cd $ORACLE_HOME/rdbms/lib
make -f ins_rdbms.mk lbac_off ioracle

-- Author : Robinson Cheng
-- Blog :
-- DB Forum :

Step 2
$ sqlplus "/ as sysdba"
SQL> startup migrate
SQL> @?/rdbms/admin/catnools.sql
SQL> shutdown immediate
SQL> startup
SQL> select * from v$version where rownum

BANNER
--------------------------------------------------------------------------------
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production

相关阅读：

SPFILE 错误导致数据库无法启动(ORA-01565)

ORA-01172、ORA-01151错误处理

ORA-00600 [2662]错误解决

linux

Statement

The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn

Explain the role of InnoDB redo logs and undo logs.Apr 15, 2025 am 12:16 AM

InnoDB uses redologs and undologs to ensure data consistency and reliability. 1.redologs record data page modification to ensure crash recovery and transaction persistence. 2.undologs records the original data value and supports transaction rollback and MVCC.

What are the key metrics to look for in an EXPLAIN output (type, key, rows, Extra)?Apr 15, 2025 am 12:15 AM

Key metrics for EXPLAIN commands include type, key, rows, and Extra. 1) The type reflects the access type of the query. The higher the value, the higher the efficiency, such as const is better than ALL. 2) The key displays the index used, and NULL indicates no index. 3) rows estimates the number of scanned rows, affecting query performance. 4) Extra provides additional information, such as Usingfilesort prompts that it needs to be optimized.

What is the Using temporary status in EXPLAIN and how to avoid it?Apr 15, 2025 am 12:14 AM

Usingtemporary indicates that the need to create temporary tables in MySQL queries, which are commonly found in ORDERBY using DISTINCT, GROUPBY, or non-indexed columns. You can avoid the occurrence of indexes and rewrite queries and improve query performance. Specifically, when Usingtemporary appears in EXPLAIN output, it means that MySQL needs to create temporary tables to handle queries. This usually occurs when: 1) deduplication or grouping when using DISTINCT or GROUPBY; 2) sort when ORDERBY contains non-index columns; 3) use complex subquery or join operations. Optimization methods include: 1) ORDERBY and GROUPB

Describe the different SQL transaction isolation levels (Read Uncommitted, Read Committed, Repeatable Read, Serializable) and their implications in MySQL/InnoDB.Apr 15, 2025 am 12:11 AM

MySQL/InnoDB supports four transaction isolation levels: ReadUncommitted, ReadCommitted, RepeatableRead and Serializable. 1.ReadUncommitted allows reading of uncommitted data, which may cause dirty reading. 2. ReadCommitted avoids dirty reading, but non-repeatable reading may occur. 3.RepeatableRead is the default level, avoiding dirty reading and non-repeatable reading, but phantom reading may occur. 4. Serializable avoids all concurrency problems but reduces concurrency. Choosing the appropriate isolation level requires balancing data consistency and performance requirements.

MySQL vs. Other Databases: Comparing the OptionsApr 15, 2025 am 12:08 AM

MySQL is suitable for web applications and content management systems and is popular for its open source, high performance and ease of use. 1) Compared with PostgreSQL, MySQL performs better in simple queries and high concurrent read operations. 2) Compared with Oracle, MySQL is more popular among small and medium-sized enterprises because of its open source and low cost. 3) Compared with Microsoft SQL Server, MySQL is more suitable for cross-platform applications. 4) Unlike MongoDB, MySQL is more suitable for structured data and transaction processing.

How does MySQL index cardinality affect query performance?Apr 14, 2025 am 12:18 AM

MySQL index cardinality has a significant impact on query performance: 1. High cardinality index can more effectively narrow the data range and improve query efficiency; 2. Low cardinality index may lead to full table scanning and reduce query performance; 3. In joint index, high cardinality sequences should be placed in front to optimize query.

MySQL: Resources and Tutorials for New UsersApr 14, 2025 am 12:16 AM

The MySQL learning path includes basic knowledge, core concepts, usage examples, and optimization techniques. 1) Understand basic concepts such as tables, rows, columns, and SQL queries. 2) Learn the definition, working principles and advantages of MySQL. 3) Master basic CRUD operations and advanced usage, such as indexes and stored procedures. 4) Familiar with common error debugging and performance optimization suggestions, such as rational use of indexes and optimization queries. Through these steps, you will have a full grasp of the use and optimization of MySQL.

Real-World MySQL: Examples and Use CasesApr 14, 2025 am 12:15 AM

MySQL's real-world applications include basic database design and complex query optimization. 1) Basic usage: used to store and manage user data, such as inserting, querying, updating and deleting user information. 2) Advanced usage: Handle complex business logic, such as order and inventory management of e-commerce platforms. 3) Performance optimization: Improve performance by rationally using indexes, partition tables and query caches.

See all articles