PROBLEM:
/u01/app/oracle/product/11.2.0/grid/rdbms/audit $ rm *.aud
-bash: /bin/rm: Argument list too long
SOLUTION:
/u01/app/oracle/product/11.2.0/grid/rdbms/audit $ ls -la | grep ".aud" | awk {'print "rm "$9'} > rm_audit_log.sh
ksh rm_audit_log.sh
7 Ekim 2015 Çarşamba
[EN] Who is locking my user ?
Use the following steps, if someone is locking an oracle database user by entering wrong password.
Wrong password attemp limit is determined by FAILED_LOGIN_ATTEMPTS profile parameter.
So check it first. In our case we assume that it's value is 3.
ORA-01017: invalid username/password; logon dedied
ORA-01017: invalid username/password; logon dedied
ORA-01017: invalid username/password; logon dedied
ORA-28000: the account is locked
Wrong password attemp limit is determined by FAILED_LOGIN_ATTEMPTS profile parameter.
So check it first. In our case we assume that it's value is 3.
ORA-01017: invalid username/password; logon dedied
ORA-01017: invalid username/password; logon dedied
ORA-01017: invalid username/password; logon dedied
ORA-28000: the account is locked
[EN] ORA-01111: name for data file n is unknown - rename to correct file
PROBLEM:
On one of our physical standby database, we noticed that media recovery was stooped.
When we try to start it again we got the following errors in altertlog;
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT FROM SESSION
Attempt to start background Managed Standby Recovery process (PRODSTB)
Fri Aug 17 09:11:05 2015
MRP0 started with pid=39, OS id=8061128
MRP0: Background Managed Standby Recovery process started (PRODSTB)
started logmerger process
Fri Aug 17 09:11:10 2015
Managed Standby Recovery starting Real Time Apply
MRP0: Background Media Recovery terminated with error 1111
Errors in file /u01/app/oracle/diag/rdbms/prodstb/PRODSTB/trace/PRODSTB_pr00_7985076.trc:
ORA-01111: name for data file 24 is unknown - rename to correct file
ORA-01110: data file 24: '/u01/app/oracle/product/11.2.0.4/db/dbs/UNNAMED00024'
ORA-01157: cannot identify/lock data file 24 - see DBWR trace file
ORA-01111: name for data file 24 is unknown - rename to correct file
ORA-01110: data file 24: '/u01/app/oracle/product/11.2.0.4/db/dbs/UNNAMED00024'
Managed Standby Recovery not using Real Time Apply
Recovery Slave PR00 previously exited with exception 1111
MRP0: Background Media Recovery process shutdown (PRODSTB)
Completed: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT FROM SESSION
On one of our physical standby database, we noticed that media recovery was stooped.
When we try to start it again we got the following errors in altertlog;
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT FROM SESSION
Attempt to start background Managed Standby Recovery process (PRODSTB)
Fri Aug 17 09:11:05 2015
MRP0 started with pid=39, OS id=8061128
MRP0: Background Managed Standby Recovery process started (PRODSTB)
started logmerger process
Fri Aug 17 09:11:10 2015
Managed Standby Recovery starting Real Time Apply
MRP0: Background Media Recovery terminated with error 1111
Errors in file /u01/app/oracle/diag/rdbms/prodstb/PRODSTB/trace/PRODSTB_pr00_7985076.trc:
ORA-01111: name for data file 24 is unknown - rename to correct file
ORA-01110: data file 24: '/u01/app/oracle/product/11.2.0.4/db/dbs/UNNAMED00024'
ORA-01157: cannot identify/lock data file 24 - see DBWR trace file
ORA-01111: name for data file 24 is unknown - rename to correct file
ORA-01110: data file 24: '/u01/app/oracle/product/11.2.0.4/db/dbs/UNNAMED00024'
Managed Standby Recovery not using Real Time Apply
Recovery Slave PR00 previously exited with exception 1111
MRP0: Background Media Recovery process shutdown (PRODSTB)
Completed: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT FROM SESSION
12 Temmuz 2014 Cumartesi
[EN] ORA-00600: internal error code, arguments: [kcbtema_10], [1], [], [], [], [], [], []
ERROR:
During startup we got the following error. The version of the database is; 10.2.0.5.
SQL> startup
ORACLE instance started.
Total System Global Area 3372220416 bytes
Fixed Size 2071640 bytes
Variable Size 1291846568 bytes
Database Buffers 2046820352 bytes
Redo Buffers 31481856 bytes
Database mounted.
ORA-00600: internal error code, arguments: [kcbtema_10], [1], [], [], [], [],[], []
SQL>
Also we noticed the following entires in alertlog;
During startup we got the following error. The version of the database is; 10.2.0.5.
SQL> startup
ORACLE instance started.
Total System Global Area 3372220416 bytes
Fixed Size 2071640 bytes
Variable Size 1291846568 bytes
Database Buffers 2046820352 bytes
Redo Buffers 31481856 bytes
Database mounted.
ORA-00600: internal error code, arguments: [kcbtema_10], [1], [], [], [], [],[], []
SQL>
Also we noticed the following entires in alertlog;
28 Mayıs 2014 Çarşamba
[EN] RMAN connection error: ORA-28041: Authentication protocol internal error
$ rman target rman/xxx@db1;
Recovery Manager: Release 10.2.0.5.0 - Production on Tue May 27 18:44:36 2014
Copyright (c) 1982, 2007, Oracle. All rights reserved.
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-04005: error from target database:
ORA-28041: Authentication protocol internal error
We got this error after applying PSU12 to one of our 10.2.0.5 production database. It was on a HP-UX Itanium 64 bit server. We applied the PSU successfully, but later we noticed that it gave some WARNINGs.
Here are the warnings;
Kaydol:
Kayıtlar (Atom)