ORA-30027:Undo quota violation failed to get 92 (Bytes)

Hi All,
When running the accrual cutom report and it was taking long time and then it errors out.
Error is "ORA-30027:Undo quota violation failed to get 92 (Bytes)".
I asked Asked DBA to increase undo quota, or wait until other transactions to commit before proceeding
and DBA replied like "We have over 5GB of undo space--that's a huge amount for a single report to use".
Please let me know, any idea how to fix this issue?
Thanks,
Prasad Raju

Hi,
Please see these documents.
Note: 173698.1 - OERR: ORA-30027 Undo quota violation - failed to get %s (bytes)
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=173698.1
Note: 559624.1 - What Does Undo Quota Mean And How Can We Solve ORA-30027
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=559624.1
Regards,
Hussein

Similar Messages

Reattempt of insert after a ORA-0001 unique constraint violation

Hi,
I'm inserting into a table. The primary key on this table is made up of the user id and a one-up transaction number. Unfortunately, I cannot change the design of this table.
Because I have to query the table to get the next transaction number before I insert into the table, I sometimes get a ORA-0001 (unique constraint violation) error because some other session grabbed the next transaction number and committed before I did.
To deal with this I retry the insert, that is, read the table again for the next tran number and insert. I allow for this up to 3 times. If after the third attempt I fail again, I rollback.
I'm seeing 3 records in the table.
So here are my questions: Do I need to rollback when I get the ORA-0001 error? I thought I wouldn't have to. If I do, why? The insert failed, how could the commit statement commit 3 records?
Thanks!

No, the userid and transaction numbers are not the same (combined) for each of the 3 rows.
Here is the logic to retry again when I get a ORA-0001:
PROCEDURE insert_record(
table1_rec_in IN table1%ROWTYPE,
tran_number OUT table1.trans_number%TYPE,
attempt_number IN PLS_INTEGER)
IS
next_tran_number table1.trans_number%TYPE;
BEGIN
SELECT NVL(MAX(trans_number), 0) + 1
INTO next_tran_number
FROM table1
WHERE userid = table1_rec_in.table1_userid;
INSERT INTO table1
(userid,
trans_number,
amount,
transdate)
VALUES
(table1_rec_in.userid,
next_tran_number,
table1_rec_in.amount,
SYSDATE);
tran_number := next_tran_number;
EXCEPTION
WHEN DUP_VAL_ON_INDEX THEN
IF attempt_number < 3
THEN
DECLARE
next_attempt_number PLS_INTEGER;
BEGIN
next_attempt_number := attempt_number + 1;
insert_record(
table1_rec_in,
tran_number,
next_attempt_number);
END;
ELSE
RAISE unable_to_insert_rec;
END IF;
WHEN OTHERS THEN
RAISE unable_to_insert_rec;
END;
I'm using recursion to try the insert again. Is this the source of my problems? I don't see it and can't reproduce it.

ORA-30012: undo tablespace 'UNDOTBS' does not exist or of wrong type

OS Version : AIX 6.1
DB Version : 11.2.0.1
I am duplicating database and got below error:
contents of Memory Script:
   Alter clone database open resetlogs;
executing Memory Script
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00601: fatal error in recovery manager
RMAN-03004: fatal error during execution of command
RMAN-10041: Could not re-create polling channel context following failure.
RMAN-10024: error setting up for rpc polling
RMAN-10005: error opening cursor
RMAN-10002: ORACLE error: ORA-03114: not connected to ORACLE
RMAN-03002: failure of Duplicate Db command at 02/16/2013 17:20:02
RMAN-03015: error occurred in stored script Memory Script
RMAN-06136: ORACLE error from auxiliary database: ORA-01092: ORACLE instance terminated. Disconnection forced
ORA-30012: undo tablespace 'UNDOTBS' does not exist or of wrong type
Process ID: 44040326
Session ID: 65 Serial number: 3
Error is because in target database undo tablespace is UNDOTBS_NEW and in auxiliary database undo tablespace name in init file is UNDOTBS. I followed the meatlink doc 433992.1 which suggest following steps to recover from above error:
1) edit the parameter UNDO_MANAGEMENT to "MANUAL"
2) start database again
3) drop the UNDO tablespace
4) recreate UNDO tablespace which matches to name in init file.
5) shutdown & start DB again.
Now, i edited init file and tried to start DB and got following error:
oracore@cph-core-db01-s $ sqlplus /nolog
SQL*Plus: Release 11.2.0.1.0 Production on Sat Feb 16 17:22:11 2013
Copyright (c) 1982, 2009, Oracle. All rights reserved.
SQL> conn sys as sysdba
Enter password:
Connected to an idle instance.
SQL> startup
ORACLE instance started.
Total System Global Area 4275781632 bytes
Fixed Size                  2213632 bytes
Variable Size             822085888 bytes
Database Buffers         3439329280 bytes
Redo Buffers               12152832 bytes
Database mounted.
ORA-01113: file 1 needs media recovery
ORA-01110: data file 1: '/u04/oradata/CORE/CORE_DUP/system01.dbf'I don't want to run duplicate command with correct UNDO tablespace name. Any other work around for this ?

STARTUP MOUNT
RECOVER DATABASE USING BACKUP CONTROLFILE UNTIL CANCEL
CANCEL
ALTER DATABASE OPEN RESETLOGS
Above option is not working for CORE_DUP, i am getting very strange error, while trying to recover i am getting very strange error as below:
oracore@cph-core-db01-s $ export ORACLE_SID=CORE_DUP
SQL*Plus: Release 11.2.0.1.0 Production on Mon Feb 18 11:17:25 2013
Copyright (c) 1982, 2009, Oracle. All rights reserved.
SQL> conn sys as sysdba
Enter password:
Connected to an idle instance.
SQL> startup mount
ORACLE instance started.
Total System Global Area 4275781632 bytes
Fixed Size                  2213632 bytes
Variable Size             822085888 bytes
Database Buffers         3439329280 bytes
Redo Buffers               12152832 bytes
Database mounted.
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01139: RESETLOGS option only valid after an incomplete database recovery
SQL> recover database using backup controlfile until cancel;
ORA-00283: recovery session canceled due to errors
ORA-16433: The database must be opened in read/write mode.Primary database initfile:
event="10298 trace name context forever, level 32"
db_block_size=8192
db_file_multiblock_read_count=16
open_cursors=300
db_name=CORE
cursor_sharing='SIMILAR'
global_names=FALSE
diagnostic_dest=/u01/app/oracore/diag/CORE
#background_dump_dest=/u01/app/oracore/diag/rdbms/bdump
#core_dump_dest=/u01/app/oracore/diag/rdbms/cdump
#user_dump_dest=/u01/app/oracore/diag/rdbms/udump
control_files=("/u01/oradata/CORE/control01.ctl", "/u02/oradata/CORE/control02.ctl", "/u03/oradata/CORE/control03.ctl")
log_archive_dest_1='LOCATION=/u05/oradata/CORE/'
log_archive_format='CORE_%s%t%r.ARC'
job_queue_processes=10
compatible=11.2.0.1
processes=150
fast_start_mttr_target=300
filesystemio_options='SETALL'
pga_aggregate_target=500M
recyclebin='OFF'
remote_login_passwordfile='EXCLUSIVE'
session_cached_cursors=100
sga_target=4G
undo_management='AUTO'
undo_tablespace='UNDOTBS_NEW'
nls_date_format='DD-MON-RRRR'
nls_length_semantics='CHAR'initfile for CORE_DUP
event="10298 trace name context forever, level 32"
db_block_size=8192
db_file_multiblock_read_count=16
open_cursors=300
db_name=CORE_DUP
cursor_sharing='SIMILAR'
global_names=FALSE
diagnostic_dest=/u01/app/oracore/diag/CORE/CORE_DUP
control_files=("/u01/oradata/CORE/CORE_DUP/control01.ctl", "/u02/oradata/CORE/CORE_DUP/control02.ctl", "/u03/oradata/CORE/CORE_DUP/control03.ctl")
log_archive_dest_1='LOCATION=/u05/oradata/CORE/CORE_DUP/'
log_archive_format='CORE_DUP%s%t%r.ARC'
job_queue_processes=10
compatible=11.2.0.1
_compression_compatibility="11.2.0"
processes=150
fast_start_mttr_target=300
filesystemio_options='SETALL'
pga_aggregate_target=500M
recyclebin='OFF'
remote_login_passwordfile='EXCLUSIVE'
session_cached_cursors=100
sga_target=4G
undo_management='AUTO'
undo_tablespace='UNDOTBS'
nls_date_format='DD-MON-RRRR'
nls_length_semantics='CHAR'
log_file_name_convert='/CORE','/CORE/CORE_DUP'
db_file_name_convert='/CORE','/CORE/CORE_DUP'Duplicate steps are as:
oracore@cph-core-db01-s $ rman target sys/zzzz@core catalog rmantst10/zzzzz@catdb auxiliary /
Recovery Manager: Release 11.2.0.1.0 - Production on Mon Feb 18 15:50:00 2013
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: CORE (DBID=913972022)
connected to recovery catalog database
connected to auxiliary database: CORE_DUP (not mounted)
RMAN> duplicate target database to CORE_DUP;
Starting Duplicate Db at 18-FEB-13
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID=96 device type=DISK
allocated channel: ORA_AUX_DISK_2
channel ORA_AUX_DISK_2: SID=127 device type=DISK
contents of Memory Script:
   sql clone "create spfile from memory";
executing Memory Script
sql statement: create spfile from memory
contents of Memory Script:
   shutdown clone immediate;
   startup clone nomount;
executing Memory Script
Oracle instance shut down
connected to auxiliary database (not started)
Oracle instance started
Total System Global Area    4275781632 bytes
Fixed Size                     2213632 bytes
Variable Size                838863104 bytes
Database Buffers            3422552064 bytes
Redo Buffers                  12152832 bytes
contents of Memory Script:
   sql clone "alter system set db_name =
''CORE'' comment=
''Modified by RMAN duplicate'' scope=spfile";
   sql clone "alter system set db_unique_name =
''CORE_DUP'' comment=
''Modified by RMAN duplicate'' scope=spfile";
   shutdown clone immediate;
   startup clone force nomount
   restore clone primary controlfile;
   alter clone database mount;
executing Memory Script
sql statement: alter system set db_name = ''CORE'' comment= ''Modified by RMAN duplicate'' scope=spfile
sql statement: alter system set db_unique_name = ''CORE_DUP'' comment= ''Modified by RMAN duplicate'' scope=spfile
Oracle instance shut down
Oracle instance started
Total System Global Area    4275781632 bytes
Fixed Size                     2213632 bytes
Variable Size                838863104 bytes
Database Buffers            3422552064 bytes
Redo Buffers                  12152832 bytes
Starting restore at 18-FEB-13
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID=96 device type=DISK
allocated channel: ORA_AUX_DISK_2
channel ORA_AUX_DISK_2: SID=127 device type=DISK
channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: restoring control file
channel ORA_AUX_DISK_1: reading from backup piece /oraclebackup/CORE/DF_L1_CORE_16022013_5fo246k3_175_1
channel ORA_AUX_DISK_1: piece handle=/oraclebackup/CORE/DF_L1_CORE_16022013_5fo246k3_175_1 tag=LEVEL1
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:03
output file name=/u01/oradata/CORE/CORE_DUP/control01.ctl
output file name=/u02/oradata/CORE/CORE_DUP/control02.ctl
output file name=/u03/oradata/CORE/CORE_DUP/control03.ctl
Finished restore at 18-FEB-13
database mounted
contents of Memory Script:
   set until scn 1217601;
   set newname for datafile 1 to
"/u04/oradata/CORE/CORE_DUP/system01.dbf";
   set newname for datafile 2 to
"/u04/oradata/CORE/CORE_DUP/sysaux01.dbf";
   set newname for datafile 4 to
"/u04/oradata/CORE/CORE_DUP/users01.dbf";
   set newname for datafile 5 to
"/u04/oradata/CORE/CORE_DUP/users02.dbf";
   set newname for datafile 6 to
"/u04/oradata/CORE/CORE_DUP/users03.dbf";
   set newname for datafile 9 to
"/u04/oradata/CORE/CORE_DUP/undotbs_new01.dbf";
   restore
   clone database
executing Memory Script
executing command: SET until clause
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
Starting restore at 18-FEB-13
using channel ORA_AUX_DISK_1
using channel ORA_AUX_DISK_2
channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_AUX_DISK_1: restoring datafile 00004 to /u04/oradata/CORE/CORE_DUP/users01.dbf
channel ORA_AUX_DISK_1: restoring datafile 00005 to /u04/oradata/CORE/CORE_DUP/users02.dbf
channel ORA_AUX_DISK_1: restoring datafile 00006 to /u04/oradata/CORE/CORE_DUP/users03.dbf
channel ORA_AUX_DISK_1: reading from backup piece /oraclebackup/CORE/DF_L0_CORE_16022013_55o246fe_165_1
channel ORA_AUX_DISK_2: starting datafile backup set restore
channel ORA_AUX_DISK_2: specifying datafile(s) to restore from backup set
channel ORA_AUX_DISK_2: restoring datafile 00001 to /u04/oradata/CORE/CORE_DUP/system01.dbf
channel ORA_AUX_DISK_2: restoring datafile 00002 to /u04/oradata/CORE/CORE_DUP/sysaux01.dbf
channel ORA_AUX_DISK_2: restoring datafile 00009 to /u04/oradata/CORE/CORE_DUP/undotbs_new01.dbf
channel ORA_AUX_DISK_2: reading from backup piece /oraclebackup/CORE/DF_L0_CORE_16022013_56o246fe_166_1
channel ORA_AUX_DISK_2: piece handle=/oraclebackup/CORE/DF_L0_CORE_16022013_56o246fe_166_1 tag=LEVEL0
channel ORA_AUX_DISK_2: restored backup piece 1
channel ORA_AUX_DISK_2: restore complete, elapsed time: 00:01:15
channel ORA_AUX_DISK_1: piece handle=/oraclebackup/CORE/DF_L0_CORE_16022013_55o246fe_165_1 tag=LEVEL0
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:01:35
Finished restore at 18-FEB-13
contents of Memory Script:
   switch clone datafile all;
executing Memory Script
datafile 1 switched to datafile copy
input datafile copy RECID=24 STAMP=807724355 file name=/u04/oradata/CORE/CORE_DUP/system01.dbf
datafile 2 switched to datafile copy
input datafile copy RECID=25 STAMP=807724355 file name=/u04/oradata/CORE/CORE_DUP/sysaux01.dbf
datafile 4 switched to datafile copy
input datafile copy RECID=26 STAMP=807724356 file name=/u04/oradata/CORE/CORE_DUP/users01.dbf
datafile 5 switched to datafile copy
input datafile copy RECID=27 STAMP=807724356 file name=/u04/oradata/CORE/CORE_DUP/users02.dbf
datafile 6 switched to datafile copy
input datafile copy RECID=28 STAMP=807724356 file name=/u04/oradata/CORE/CORE_DUP/users03.dbf
datafile 9 switched to datafile copy
input datafile copy RECID=29 STAMP=807724356 file name=/u04/oradata/CORE/CORE_DUP/undotbs_new01.dbf
contents of Memory Script:
   set until scn 1217601;
   recover
   clone database
    delete archivelog
executing Memory Script
executing command: SET until clause
Starting recover at 18-FEB-13
using channel ORA_AUX_DISK_1
using channel ORA_AUX_DISK_2
channel ORA_AUX_DISK_1: starting incremental datafile backup set restore
channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
destination for restore of datafile 00001: /u04/oradata/CORE/CORE_DUP/system01.dbf
destination for restore of datafile 00002: /u04/oradata/CORE/CORE_DUP/sysaux01.dbf
destination for restore of datafile 00009: /u04/oradata/CORE/CORE_DUP/undotbs_new01.dbf
channel ORA_AUX_DISK_1: reading from backup piece /oraclebackup/CORE/DF_L1_CORE_16022013_5eo246k2_174_1
channel ORA_AUX_DISK_2: starting incremental datafile backup set restore
channel ORA_AUX_DISK_2: specifying datafile(s) to restore from backup set
destination for restore of datafile 00004: /u04/oradata/CORE/CORE_DUP/users01.dbf
destination for restore of datafile 00005: /u04/oradata/CORE/CORE_DUP/users02.dbf
destination for restore of datafile 00006: /u04/oradata/CORE/CORE_DUP/users03.dbf
channel ORA_AUX_DISK_2: reading from backup piece /oraclebackup/CORE/DF_L1_CORE_16022013_5do246k2_173_1
channel ORA_AUX_DISK_1: piece handle=/oraclebackup/CORE/DF_L1_CORE_16022013_5eo246k2_174_1 tag=LEVEL1
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
channel ORA_AUX_DISK_2: piece handle=/oraclebackup/CORE/DF_L1_CORE_16022013_5do246k2_173_1 tag=LEVEL1
channel ORA_AUX_DISK_2: restored backup piece 1
channel ORA_AUX_DISK_2: restore complete, elapsed time: 00:00:01
starting media recovery
archived log for thread 1 with sequence 1718 is already on disk as file /u05/oradata/CORE/CORE_17181807276264.ARC
archived log for thread 1 with sequence 1719 is already on disk as file /u05/oradata/CORE/CORE_17191807276264.ARC
archived log for thread 1 with sequence 1720 is already on disk as file /u05/oradata/CORE/CORE_17201807276264.ARC
archived log for thread 1 with sequence 1721 is already on disk as file /u05/oradata/CORE/CORE_17211807276264.ARC
archived log for thread 1 with sequence 1722 is already on disk as file /u05/oradata/CORE/CORE_17221807276264.ARC
archived log for thread 1 with sequence 1723 is already on disk as file /u05/oradata/CORE/CORE_17231807276264.ARC
archived log for thread 1 with sequence 1724 is already on disk as file /u05/oradata/CORE/CORE_17241807276264.ARC
archived log for thread 1 with sequence 1725 is already on disk as file /u05/oradata/CORE/CORE_17251807276264.ARC
archived log for thread 1 with sequence 1726 is already on disk as file /u05/oradata/CORE/CORE_17261807276264.ARC
archived log for thread 1 with sequence 1727 is already on disk as file /u05/oradata/CORE/CORE_17271807276264.ARC
archived log for thread 1 with sequence 1728 is already on disk as file /u05/oradata/CORE/CORE_17281807276264.ARC
archived log for thread 1 with sequence 1729 is already on disk as file /u05/oradata/CORE/CORE_17291807276264.ARC
archived log for thread 1 with sequence 1730 is already on disk as file /u05/oradata/CORE/CORE_17301807276264.ARC
archived log for thread 1 with sequence 1731 is already on disk as file /u05/oradata/CORE/CORE_17311807276264.ARC
archived log for thread 1 with sequence 1732 is already on disk as file /u05/oradata/CORE/CORE_17321807276264.ARC
archived log for thread 1 with sequence 1733 is already on disk as file /u05/oradata/CORE/CORE_17331807276264.ARC
archived log for thread 1 with sequence 1734 is already on disk as file /u05/oradata/CORE/CORE_17341807276264.ARC
archived log for thread 1 with sequence 1735 is already on disk as file /u05/oradata/CORE/CORE_17351807276264.ARC
archived log for thread 1 with sequence 1736 is already on disk as file /u05/oradata/CORE/CORE_17361807276264.ARC
archived log for thread 1 with sequence 1737 is already on disk as file /u05/oradata/CORE/CORE_17371807276264.ARC
archived log for thread 1 with sequence 1738 is already on disk as file /u05/oradata/CORE/CORE_17381807276264.ARC
archived log for thread 1 with sequence 1739 is already on disk as file /u05/oradata/CORE/CORE_17391807276264.ARC
archived log for thread 1 with sequence 1740 is already on disk as file /u05/oradata/CORE/CORE_17401807276264.ARC
archived log for thread 1 with sequence 1741 is already on disk as file /u05/oradata/CORE/CORE_17411807276264.ARC
archived log for thread 1 with sequence 1742 is already on disk as file /u05/oradata/CORE/CORE_17421807276264.ARC
archived log for thread 1 with sequence 1743 is already on disk as file /u05/oradata/CORE/CORE_17431807276264.ARC
archived log for thread 1 with sequence 1744 is already on disk as file /u05/oradata/CORE/CORE_17441807276264.ARC
channel ORA_AUX_DISK_1: starting archived log restore to default destination
channel ORA_AUX_DISK_1: restoring archived log
archived log thread=1 sequence=1710
channel ORA_AUX_DISK_1: reading from backup piece /oraclebackup/CORE/ARC_1HR_CORE_16022013_5jo24jp8_179_1
channel ORA_AUX_DISK_2: starting archived log restore to default destination
channel ORA_AUX_DISK_2: restoring archived log
archived log thread=1 sequence=1711
channel ORA_AUX_DISK_2: restoring archived log
archived log thread=1 sequence=1712
channel ORA_AUX_DISK_2: restoring archived log
archived log thread=1 sequence=1713
channel ORA_AUX_DISK_2: restoring archived log
archived log thread=1 sequence=1714
channel ORA_AUX_DISK_2: restoring archived log
archived log thread=1 sequence=1715
channel ORA_AUX_DISK_2: restoring archived log
archived log thread=1 sequence=1716
channel ORA_AUX_DISK_2: restoring archived log
archived log thread=1 sequence=1717
channel ORA_AUX_DISK_2: reading from backup piece /oraclebackup/CORE/ARC_1HR_CORE_18022013_5ko296uf_180_1
channel ORA_AUX_DISK_1: piece handle=/oraclebackup/CORE/ARC_1HR_CORE_16022013_5jo24jp8_179_1 tag=ARC_1HR
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17101807276264.ARC thread=1 sequence=1710
channel clone_default: deleting archived log(s)
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17101807276264.ARC RECID=3041 STAMP=807724360
channel ORA_AUX_DISK_2: piece handle=/oraclebackup/CORE/ARC_1HR_CORE_18022013_5ko296uf_180_1 tag=ARC_1HR
channel ORA_AUX_DISK_2: restored backup piece 1
channel ORA_AUX_DISK_2: restore complete, elapsed time: 00:00:08
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17111807276264.ARC thread=1 sequence=1711
channel clone_default: deleting archived log(s)
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17111807276264.ARC RECID=3042 STAMP=807724362
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17121807276264.ARC thread=1 sequence=1712
channel clone_default: deleting archived log(s)
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17121807276264.ARC RECID=3043 STAMP=807724363
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17131807276264.ARC thread=1 sequence=1713
channel clone_default: deleting archived log(s)
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17131807276264.ARC RECID=3044 STAMP=807724367
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17141807276264.ARC thread=1 sequence=1714
channel clone_default: deleting archived log(s)
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17141807276264.ARC RECID=3048 STAMP=807724367
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17151807276264.ARC thread=1 sequence=1715
channel clone_default: deleting archived log(s)
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17151807276264.ARC RECID=3046 STAMP=807724367
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17161807276264.ARC thread=1 sequence=1716
channel clone_default: deleting archived log(s)
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17161807276264.ARC RECID=3045 STAMP=807724367
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17171807276264.ARC thread=1 sequence=1717
channel clone_default: deleting archived log(s)
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17171807276264.ARC RECID=3047 STAMP=807724367
archived log file name=/u05/oradata/CORE/CORE_17181807276264.ARC thread=1 sequence=1718
archived log file name=/u05/oradata/CORE/CORE_17191807276264.ARC thread=1 sequence=1719
archived log file name=/u05/oradata/CORE/CORE_17201807276264.ARC thread=1 sequence=1720
archived log file name=/u05/oradata/CORE/CORE_17211807276264.ARC thread=1 sequence=1721
archived log file name=/u05/oradata/CORE/CORE_17221807276264.ARC thread=1 sequence=1722
archived log file name=/u05/oradata/CORE/CORE_17231807276264.ARC thread=1 sequence=1723
archived log file name=/u05/oradata/CORE/CORE_17241807276264.ARC thread=1 sequence=1724
archived log file name=/u05/oradata/CORE/CORE_17251807276264.ARC thread=1 sequence=1725
archived log file name=/u05/oradata/CORE/CORE_17261807276264.ARC thread=1 sequence=1726
archived log file name=/u05/oradata/CORE/CORE_17271807276264.ARC thread=1 sequence=1727
archived log file name=/u05/oradata/CORE/CORE_17281807276264.ARC thread=1 sequence=1728
archived log file name=/u05/oradata/CORE/CORE_17291807276264.ARC thread=1 sequence=1729
archived log file name=/u05/oradata/CORE/CORE_17301807276264.ARC thread=1 sequence=1730
archived log file name=/u05/oradata/CORE/CORE_17311807276264.ARC thread=1 sequence=1731
archived log file name=/u05/oradata/CORE/CORE_17321807276264.ARC thread=1 sequence=1732
archived log file name=/u05/oradata/CORE/CORE_17331807276264.ARC thread=1 sequence=1733
archived log file name=/u05/oradata/CORE/CORE_17341807276264.ARC thread=1 sequence=1734
archived log file name=/u05/oradata/CORE/CORE_17351807276264.ARC thread=1 sequence=1735
archived log file name=/u05/oradata/CORE/CORE_17361807276264.ARC thread=1 sequence=1736
archived log file name=/u05/oradata/CORE/CORE_17371807276264.ARC thread=1 sequence=1737
archived log file name=/u05/oradata/CORE/CORE_17381807276264.ARC thread=1 sequence=1738
archived log file name=/u05/oradata/CORE/CORE_17391807276264.ARC thread=1 sequence=1739
archived log file name=/u05/oradata/CORE/CORE_17401807276264.ARC thread=1 sequence=1740
archived log file name=/u05/oradata/CORE/CORE_17411807276264.ARC thread=1 sequence=1741
archived log file name=/u05/oradata/CORE/CORE_17421807276264.ARC thread=1 sequence=1742
archived log file name=/u05/oradata/CORE/CORE_17431807276264.ARC thread=1 sequence=1743
archived log file name=/u05/oradata/CORE/CORE_17441807276264.ARC thread=1 sequence=1744
media recovery complete, elapsed time: 00:00:33
Finished recover at 18-FEB-13
contents of Memory Script:
   shutdown clone immediate;
   startup clone nomount;
   sql clone "alter system set db_name =
''CORE_DUP'' comment=
''Reset to original value by RMAN'' scope=spfile";
   sql clone "alter system reset db_unique_name scope=spfile";
   shutdown clone immediate;
   startup clone nomount;
executing Memory Script
database dismounted
Oracle instance shut down
connected to auxiliary database (not started)
Oracle instance started
Total System Global Area    4275781632 bytes
Fixed Size                     2213632 bytes
Variable Size                838863104 bytes
Database Buffers            3422552064 bytes
Redo Buffers                  12152832 bytes
sql statement: alter system set db_name = ''CORE_DUP'' comment= ''Reset to original value by RMAN'' scope=spfile
sql statement: alter system reset db_unique_name scope=spfile
Oracle instance shut down
connected to auxiliary database (not started)
Oracle instance started
Total System Global Area    4275781632 bytes
Fixed Size                     2213632 bytes
Variable Size                838863104 bytes
Database Buffers            3422552064 bytes
Redo Buffers                  12152832 bytes
sql statement: CREATE CONTROLFILE REUSE SET DATABASE "CORE_DUP" RESETLOGS ARCHIVELOG
MAXLOGFILES     32
MAXLOGMEMBERS      4
MAXDATAFILES      500
MAXINSTANCES     1
MAXLOGHISTORY     2298
LOGFILE
GROUP 1 ( '/u02/oradata/CORE/CORE_DUP/redo01a.log', '/u03/oradata/CORE/CORE_DUP/redo01b.log' ) SIZE 10 M REUSE,
GROUP 2 ( '/u02/oradata/CORE/CORE_DUP/redo02a.log', '/u03/oradata/CORE/CORE_DUP/redo02b.log' ) SIZE 10 M REUSE,
GROUP 3 ( '/u02/oradata/CORE/CORE_DUP/redo03a.log', '/u03/oradata/CORE/CORE_DUP/redo03b.log' ) SIZE 10 M REUSE
DATAFILE
'/u04/oradata/CORE/CORE_DUP/system01.dbf'
CHARACTER SET AL32UTF8
contents of Memory Script:
   set newname for tempfile 1 to
"/u04/oradata/CORE/CORE_DUP/temp01.dbf";
   switch clone tempfile all;
   catalog clone datafilecopy "/u04/oradata/CORE/CORE_DUP/sysaux01.dbf",
"/u04/oradata/CORE/CORE_DUP/users01.dbf",
"/u04/oradata/CORE/CORE_DUP/users02.dbf",
"/u04/oradata/CORE/CORE_DUP/users03.dbf",
"/u04/oradata/CORE/CORE_DUP/undotbs_new01.dbf";
   switch clone datafile all;
executing Memory Script
executing command: SET NEWNAME
renamed tempfile 1 to /u04/oradata/CORE/CORE_DUP/temp01.dbf in control file
cataloged datafile copy
datafile copy file name=/u04/oradata/CORE/CORE_DUP/sysaux01.dbf RECID=1 STAMP=807724423
cataloged datafile copy
datafile copy file name=/u04/oradata/CORE/CORE_DUP/users01.dbf RECID=2 STAMP=807724423
cataloged datafile copy
datafile copy file name=/u04/oradata/CORE/CORE_DUP/users02.dbf RECID=3 STAMP=807724423
cataloged datafile copy
datafile copy file name=/u04/oradata/CORE/CORE_DUP/users03.dbf RECID=4 STAMP=807724423
cataloged datafile copy
datafile copy file name=/u04/oradata/CORE/CORE_DUP/undotbs_new01.dbf RECID=5 STAMP=807724423
datafile 2 switched to datafile copy
input datafile copy RECID=1 STAMP=807724423 file name=/u04/oradata/CORE/CORE_DUP/sysaux01.dbf
datafile 4 switched to datafile copy
input datafile copy RECID=2 STAMP=807724423 file name=/u04/oradata/CORE/CORE_DUP/users01.dbf
datafile 5 switched to datafile copy
input datafile copy RECID=3 STAMP=807724423 file name=/u04/oradata/CORE/CORE_DUP/users02.dbf
datafile 6 switched to datafile copy
input datafile copy RECID=4 STAMP=807724423 file name=/u04/oradata/CORE/CORE_DUP/users03.dbf
datafile 9 switched to datafile copy
input datafile copy RECID=5 STAMP=807724423 file name=/u04/oradata/CORE/CORE_DUP/undotbs_new01.dbf
contents of Memory Script:
   Alter clone database open resetlogs;
executing Memory Script
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00601: fatal error in recovery manager
RMAN-03004: fatal error during execution of command
RMAN-10041: Could not re-create polling channel context following failure.
RMAN-10024: error setting up for rpc polling
RMAN-10005: error opening cursor
RMAN-10002: ORACLE error: ORA-03114: not connected to ORACLE
RMAN-03002: failure of Duplicate Db command at 02/18/2013 15:53:50
RMAN-03015: error occurred in stored script Memory Script
RMAN-06136: ORACLE error from auxiliary database: ORA-01092: ORACLE instance terminated. Disconnection forced
ORA-30012: undo tablespace 'UNDOTBS' does not exist or of wrong type
Process ID: 3670170
Session ID: 33 Serial number: 7
oracore@cph-core-db01-s $

Database won't start! ORA-12578: TNS:wallet open failed...HELP!

I went to "bounce" (shutdown immediate -> startup)a database because something had pegged the cpu at 100% and no users were active and got tyhe following errors...
SQL*Plus: Release 11.2.0.1.0 Production on Wed Oct 26 13:35:53 2011
Copyright (c) 1982, 2010, Oracle. All rights reserved.
Enter user-name: sys as sysdba
Enter password:
Connected to an idle instance.
SQL> startup
ORACLE instance started.
Total System Global Area 778387456 bytes
Fixed Size 1374808 bytes
Variable Size 503317928 bytes
Database Buffers 260046848 bytes
Redo Buffers 13647872 bytes
Database mounted.
ORA-01092: ORACLE instance terminated. Disconnection forced
ORA-12578: TNS:wallet open failed
Process ID: 4756
Session ID: 1 Serial number: 5
SQL>
In Alert.log:
Starting ORACLE instance (normal)
Wed Oct 26 09:17:31 2011
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 2
Using LOG_ARCHIVE_DEST_1 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BR
ILAT =84
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options.
Using parameter settings in server-side spfile E:\ORACLE\PRODUCT\11.2.0\DBHOME_1\DATABASE\SPFILEORCL.ORA
System parameters with non-default values:
processes = 500
memory_target = 1232M
control_files = "E:\ORACLE\ORADATA\ORCL\CONTROL01.CTL"
control_files = "E:\ORACLE\FLASH_RECOVERY_AREA\ORCL\CONTROL02.CTL"
db_block_size = 8192
compatible = "11.2.0.0.0"
log_buffer = 10485760
db_recovery_file_dest = "E:\Oracle\flash_recovery_area"
db_recovery_file_dest_size= 3852M
undo_tablespace = "UNDOTBS1"
remote_login_passwordfile= "EXCLUSIVE"
db_domain = "accounts.cdcr.ca.gov"
dispatchers = "(PROTOCOL=TCP) (SERVICE=orclXDB)"
local_listener = "LISTENER_ORCL"
session_cached_cursors = 200
job_queue_processes = 1000
audit_file_dest = "E:\ORACLE\ADMIN\ORCL\ADUMP"
audit_trail = "DB"
db_name = "orcl"
open_cursors = 300
diagnostic_dest = "E:\ORACLE"
Wed Oct 26 09:17:40 2011
PMON started with pid=2, OS id=3108
Wed Oct 26 09:17:40 2011
VKTM started with pid=3, OS id=3112 at elevated priority
VKTM running at (10)millisec precision with DBRM quantum (100)ms
Wed Oct 26 09:17:40 2011
GEN0 started with pid=4, OS id=3116
Wed Oct 26 09:17:40 2011
DIAG started with pid=5, OS id=3128
Wed Oct 26 09:17:40 2011
DBRM started with pid=6, OS id=3136
Wed Oct 26 09:17:41 2011
PSP0 started with pid=7, OS id=3140
Wed Oct 26 09:17:41 2011
DIA0 started with pid=8, OS id=3144
Wed Oct 26 09:17:41 2011
MMAN started with pid=9, OS id=3148
Wed Oct 26 09:17:41 2011
DBW0 started with pid=10, OS id=3160
Wed Oct 26 09:17:41 2011
LGWR started with pid=11, OS id=3168
Wed Oct 26 09:17:41 2011
CKPT started with pid=12, OS id=3176
Wed Oct 26 09:17:41 2011
SMON started with pid=13, OS id=3184
Wed Oct 26 09:17:41 2011
RECO started with pid=14, OS id=3192
Wed Oct 26 09:17:42 2011
MMON started with pid=15, OS id=3196
Wed Oct 26 09:17:42 2011
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
Wed Oct 26 09:17:42 2011
MMNL started with pid=16, OS id=3200
starting up 1 shared server(s) ...
ORACLE_BASE from environment = E:\Oracle
Wed Oct 26 09:17:45 2011
alter database mount exclusive
Wed Oct 26 09:17:53 2011
Successful mount of redo thread 1, with mount id 1293322043
Database mounted in Exclusive Mode
Lost write protection disabled
Wed Oct 26 09:17:55 2011
Completed: alter database mount exclusive
alter database open
Beginning crash recovery of 1 threads
Started redo scan
Completed redo scan
read 0 KB redo, 0 data blocks need recovery
Started redo application at
Thread 1: logseq 1019, block 2, scn 15641501
Recovery of Online Redo Log: Thread 1 Group 2 Seq 1019 Reading mem 0
Mem# 0: E:\ORACLE\ORADATA\ORCL\REDO02.LOG
Completed redo application of 0.00MB
Completed crash recovery at
Thread 1: logseq 1019, block 3, scn 15661503
0 data blocks read, 0 data blocks written, 0 redo k-bytes read
Wed Oct 26 09:18:06 2011
Thread 1 advanced to log sequence 1020 (thread open)
Thread 1 opened at log sequence 1020
Current log# 3 seq# 1020 mem# 0: E:\ORACLE\ORADATA\ORCL\REDO03.LOG
Successful open of redo thread 1
Wed Oct 26 09:18:08 2011
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Wed Oct 26 09:18:08 2011
SMON: enabling cache recovery
Errors in file e:\oracle\diag\rdbms\orcl\orcl\trace\orcl_ora_3276.trc:
ORA-12578: TNS:wallet open failed
Errors in file e:\oracle\diag\rdbms\orcl\orcl\trace\orcl_ora_3276.trc:
ORA-12578: TNS:wallet open failed
Error 12578 happened during db open, shutting down database
USER (ospid: 3276): terminating the instance due to error 12578
Instance terminated by USER, pid = 3276
ORA-1092 signalled during: alter database open...
opiodr aborting process unknown ospid (3276) as a result of ORA-1092
Wed Oct 26 09:18:13 2011
ORA-1092 : opitsk aborting process
In the trace file:
Trace file e:\oracle\diag\rdbms\orcl\orcl\trace\orcl_ora_3276.trc
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Windows NT Version V6.0 Service Pack 1
CPU : 1 - type 586, 1 Physical Cores
Process Affinity : 0x0x00000000
Memory (Avail/Total): Ph:5079M/6142M, Ph+PgF:10214M/12444M, VA:1034M/2047M
VM name : VMWare Version (6)
Instance name: orcl
Redo thread mounted by this instance: 1
Oracle process number: 19
Windows thread id: 3276, image: ORACLE.EXE (SHAD)
*** 2011-10-26 09:18:01.283
*** SESSION ID:(1.3) 2011-10-26 09:18:01.283
*** CLIENT ID:() 2011-10-26 09:18:01.283
*** SERVICE NAME:() 2011-10-26 09:18:01.283
*** MODULE NAME:(oradim.exe) 2011-10-26 09:18:01.283
*** ACTION NAME:() 2011-10-26 09:18:01.283
Thread 1 checkpoint: logseq 1019, block 2, scn 15641501
on-disk rba: logseq 1016, block 24845, scn 15581487
start recovery at logseq 1019, block 2, scn 15641501
*** 2011-10-26 09:18:01.751
Started writing zeroblks thread 1 seq 1019 blocks 3-10
*** 2011-10-26 09:18:02.329
Completed writing zeroblks thread 1 seq 1019
*** 2011-10-26 09:18:02.876
==== Redo read statistics for thread 1 ====
Total physical reads (from disk and memory): 4096Kb
-- Redo read_disk statistics --
Read rate (ASYNC): 0Kb in 1.55s => 0.00 Mb/sec
Longest record: 0Kb, moves: 0/1 (0%)
Longest LWN: 0Kb, moves: 0/1 (0%), moved: 0Mb
Last redo scn: 0x0000.00eeab9e (15641502)
----- Recovery Hash Table Statistics ---------
Hash table buckets = 32768
Longest hash chain = 0
Average hash chain = 0/0 = 0.0
Max compares per lookup = 0
Avg compares per lookup = 0/0 = 0.0
*** 2011-10-26 09:18:03.626
KCRA: start recovery claims for 0 data blocks
*** 2011-10-26 09:18:04.094
KCRA: blocks processed = 0/0, claimed = 0, eliminated = 0
*** 2011-10-26 09:18:04.891
Recovery of Online Redo Log: Thread 1 Group 2 Seq 1019 Reading mem 0
*** 2011-10-26 09:18:04.984
Completed redo application of 0.00MB
*** 2011-10-26 09:18:04.984
Completed recovery checkpoint
IR RIA: redo_size 0 bytes, time_taken 314 ms
----- Recovery Hash Table Statistics ---------
Hash table buckets = 32768
Longest hash chain = 0
Average hash chain = 0/0 = 0.0
Max compares per lookup = 0
Avg compares per lookup = 0/0 = 0.0
Recovery sets nab of thread 1 seq 1019 to 3 with 8 zeroblks
*** 2011-10-26 09:18:11.466
ORA-12578: TNS:wallet open failed
ORA-12578: TNS:wallet open failed
*** 2011-10-26 09:18:11.497
USER (ospid: 3276): terminating the instance due to error 12578
Symbol file E:\Oracle\product\11.2.0\dbhome_1\BIN\orageneric11.SYM does not match binary.
Symbol TimeStamp=4bb5eb10, Module TimeStamp=0 are different
EnumerateLoadedModules64 failed with error -1073741819
Symbol file orageneric11.SYM does not match binary.
Symbol TimeStamp=4bb5eb10, Module TimeStamp=0 are different
Edited by: 878073 on Oct 26, 2011 1:36 PM

I found the problem...installed wallet manager that created entry in SQLNET file pointing to a wallet that did not have proper OS permissions...

PB12.5 - Oracle 11g conenction issue - Failed to get local NLS_LANG charset ID

Hi Everyone,
We have recently migrated our OS to windows 7 and orcle client to 11g since then I am getting error "Failed to get local NLS_LANG charset ID" while connecting to Oracle using the IDE. I tried to connect using O10 Oracle 10g and ORA Oracle interface as I dont see anything for 11g; result was same in both cases. Can someone please help to resolve this issue?
Following are the system details
OS - Windows 7 62 Bit
PB - 12.5 Build 2511
Oracle Client - 11g 32 bit
Thanks,
Robin

Hi Jacob,
Here is the entry fronm trace log:
/* 3/18/2014 14:17 */
(2a922fc): DIALOG CONNECT TO TRACE ORA ORACLE:
(2a922fc): LOGID=dev_testid
(2a922fc): SERVER=TESTSRV
(2a922fc): DBPARM=PBCatalogOwner='dev_testid',DisableBind=1,TrimSpaces=1(DBI_DIALOG_CONNECT) (21.246 MS / 21.246 MS)
(2a922fc): *** ERROR 999 ***(rc -1) : Failed to get local NLS_LANG charset ID.
(2a922fc): SHUTDOWN DATABASE INTERFACE:(DBI_SHUTDOWN_INTERFACE) (0.001 MS / 21.247 MS)
NLS_LANG variable set under HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ORACLE\KEY_OraClient11g_home1
Value in Registry: AMERICAN_AMERICA.WE8MSWIN1252
Value in SQL PLUS:
SQL> SELECT USERENV ('language') FROM DUAL;
USERENV('LANGUAGE')
AMERICAN_AMERICA.WE8ISO8859P1
Thanks,
Robin

ORA-47400: Command Rule violation for CONNECT on LOGON

Oracle : 11.2.0.2.0
OS : AIX
Issue : alter log throwing error
ORA-12012: error on auto execute of job "SYS"."IDX_RB$J_6640_2"
Errors in file /oradiag/diag/rdbms/p1edwni/p1edwni/trace/p1edwni_j000_8306748.trc:
ORA-12012: error on auto execute of job "SYS"."IDX_RB$J_6640_2"
ORA-47400: Command Rule violation for CONNECT on LOGON Fri May 13 03:31:30 2011 Errors in file /oradiag/diag/rdbms/p1edwni/p1edwni/trace/p1edwni_j002_7307362.trc:
ORA-12012: error on auto execute of job "SYS"."IDX_RB$J_6640_3"
Errors in file /oradiag/diag/rdbms/p1edwni/p1edwni/trace/p1edwni_j002_7307362.trc:
ORA-12012: error on auto execute of job "SYS"."IDX_RB$J_6640_3"
ORA-47400: Command Rule violation for CONNECT on LOGON
sacbidb02-prd{oracle}: cat /oradiag/diag/rdbms/p1edwni/p1edwni/trace/p1edwni_j002_7307362.trc
Trace file /oradiag/diag/rdbms/p1edwni/p1edwni/trace/p1edwni_j002_7307362.trc
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
With the Partitioning, Oracle Label Security, OLAP, Data Mining,
Oracle Database Vault and Real Application Testing options
ORACLE_HOME = /oracle/product/11202_p1edwni/server
System name: AIX
Node name: sacbidb02-prd
Release: 1
Version: 6
Machine: 00C95CD24C00
Instance name: p1edwni
Redo thread mounted by this instance: 1
Oracle process number: 260
Unix process pid: 7307362, image: oracle@sacbidb02-prd (J002)
*** 2011-05-13 03:31:30.226
*** SESSION ID:(103.43457) 2011-05-13 03:31:30.226
*** CLIENT ID:() 2011-05-13 03:31:30.226
*** SERVICE NAME:(SYS$USERS) 2011-05-13 03:31:30.226
*** MODULE NAME:() 2011-05-13 03:31:30.226
*** ACTION NAME:() 2011-05-13 03:31:30.226
ORA-12012: error on auto execute of job "SYS"."IDX_RB$J_6640_3"
ORA-47400: Command Rule violation for CONNECT on LOGON
What could be the reason and how to resolve this ?
This appears coming form Database vault
Thanks in advance

Hi:
I believe your question would be better targeted to the Database Vault forum, where you are more likely to get relevant responses. This is the Audit Vault forum, and people here would know less about that product than those on the other forum.
Regards.

SCCM Get Collection Member Fails "Failed to get members of collection. The SMS Provider reported an error"

Full Error is: "Failed to get members of collection '{Collection Name from "Initialize Data"}'.". The SMS Provider reported an error. Details: Generic failure
Orchestrator 2012 R2 7.2.84.0
Using Integration Pack 7.2 for System Center 2012 Configuration Manager
I have a Runbook that is setup to use Get Collection Members from SCCM. The fields are:
Collection: {Collection Name from "Initialize Data"}
Collection Value Type: Name
When I use the Runbook Tester (or when I try to run it myself) I get the error:
"Failed to get members of collection '{Collection Name from "Initialize Data"}'.". The SMS Provider reported an error. Details: Generic failure
I have tried using the Collection ID and I get the same error. From the Collection Property in Get Collection Members I can browse and see all the collections in SCCM, so I know the connection is working.
An example of a collection I am trying to use is this: SUM - Patch and Reboot Server - 3rd Sat 1AM . I have tried using it with quotes and single quotes as well and I get the same error.
The log file for SCCM looks like this when it fails:
CSspQueryForObject :: Execute...~ $$<SMS Provider><03-25-2014 11:34:52.904+300><thread=528 (0x210)>
~*~*~e:\nts_sccm_release\sms\siteserver\sdk_provider\smsprov\sspobjectquery.cpp(1782) : Failed to parse WQL string SELECT * FROM SMS_Collection WHERE Name = "{Collection Name from "Initialize Data"}"~*~*~ $$<SMS Provider><03-25-2014
11:34:52.904+300><thread=528 (0x210)>
~*~*~Failed to parse WQL string SELECT * FROM SMS_Collection WHERE Name = "{Collection Name from "Initialize Data"}" ~*~*~ $$<SMS Provider><03-25-2014 11:34:52.904+300><thread=528 (0x210)>
Execute WQL =SELECT * FROM SMS_Collection WHERE Name = "{Collection Name from "Initialize Data"}"~ $$<SMS Provider><03-25-2014 11:34:52.904+300><thread=528 (0x210)>
Execute SQL =~ $$<SMS Provider><03-25-2014 11:34:52.904+300><thread=528 (0x210)>
Removing Handle 1792008112 from async call map~ $$<SMS Provider><03-25-2014 11:34:52.904+300><thread=528 (0x210)>
ExecQueryAsync: COMPLETE SELECT * FROM SMS_Collection WHERE Name = "{Collection Name from "Initialize Data"}"~ $$<SMS Provider><03-25-2014 11:34:52.904+300><thread=528 (0x210)>
CExtUserContext::LeaveThread : Releasing IWbemContextPtr=1862502880~ $$<SMS Provider><03-25-2014 11:34:52.904+300><thread=528 (0x210)>
My SCCM Administrator and I are out of ideas about what else to try. Anyone have some ideas on what might be causing the issue?
MCITP | VCP4 | VCP5

Hi,
may I ask if you modified the log? Because of ...
Execute WQL =SELECT * FROM SMS_Collection WHERE Name = "{Collection Name from "Initialize Data"}"~ $$<SMS Provider><03-25-2014 11:34:52.904+300><thread=528 (0x210)>
Have you typed or subscribe the Published Data to the Field Collection in the Activity "Get Collection Member"?
It must be subscribed!: Click with right mouse key-> Subscribe->Published Data
Regards,
Stefan
www.sc-orchestrator.eu ,
Blog sc-orchestrator.eu

ORA-27146 Post/Wait Initialization failed

Hi all,
I had a problem when trying to startup 2 database at Solaris8 machine. Please help me to solve this problem.
Problem:
I have created 2 database seperately. But I couldnt started up those 2 database at the same machine. Like either one is alive but not second one. When I startup the second database, got this error message : ORA-27146 Post/Wait Initialization failed.
I have tried to increase the sizes of System file variables at /etc/system, but its not.
I dont know the calculation for those variables when I use 2 or more instances.
Environment : Solaris8 / Oracle 8.1.5.
Please let me know if you need more clarification of problem.
null

its a resources issue. change the init.ora file for resources such as db block buffers, processes, etc. you will be able to start the instance.
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Chinnadurai Periyasamy ([email protected]):
Hi all,
I had a problem when trying to startup 2 database at Solaris8 machine. Please help me to solve this problem.
Problem:
I have created 2 database seperately. But I couldnt started up those 2 database at the same machine. Like either one is alive but not second one. When I startup the second database, got this error message : ORA-27146 Post/Wait Initialization failed.
I have tried to increase the sizes of System file variables at /etc/system, but its not.
I dont know the calculation for those variables when I use 2 or more instances.
Environment : Solaris8 / Oracle 8.1.5.
Please let me know if you need more clarification of problem.
<HR></BLOCKQUOTE>
null

Backup Error ORA-12640: Authentication adapter initialization failed

Dear All,
I have scheduled full backup from DB13 and it ends up in error. The error log is attached below.
BR0204I Percentage done: 100.00%, estimated end time: 20:12
BR0001I **************************************************
BR0280I BRBACKUP time stamp: 2009-06-03 20.12.52
BR0317I 'Alter tablespace SYSTEM end backup' successful
BR0280I BRBACKUP time stamp: 2009-06-03 20.12.56
BR0530I Cataloging backups of all database files...
BR0278E Command output of 'E:\oracle\SID\102\BIN\rman nocatalog':
Recovery Manager: Release 10.2.0.2.0 - Production on Wed Jun 3 20:12:57 200
Copyright (c) 1982, 2005, Oracle. All rights reserved.
RMAN>
RMAN> connect target *
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
ORA-12640: Authentication adapter initialization failed
RMAN> *end-of-file*
RMAN>
host command complete
RMAN> 2> 3> 4> 5> 6> 7> 8> 9> 10> 11> 12> 13> 14> 15> 16> 17> 18> 19> 20> 2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of catalog command at 06/03/2009 20:12:58
RMAN-06171: not connected to target database
RMAN>
Recovery Manager complete.
BR0280I BRBACKUP time stamp: 2009-06-03 20.12.58
BR0279E Return code from 'E:\oracle\SID\102\BIN\rman nocatalog': 1
BR0536E RMAN call for database instance DEV failed
BR0280I BRBACKUP time stamp: 2009-06-03 20.12.58
BR0532E Cataloging backups of all database files failed
BR0056I End of database backup: beasixaz.fnd 2009-06-03 20.12.58
BR0280I BRBACKUP time stamp: 2009-06-03 20.12.58
BR0054I BRBACKUP terminated with errors
BR0280I BRBACKUP time stamp: 2009-06-03 20.12.58
I have tried upgrading Brtools as per suggestion from SAP but in vain. All the services run under administrator account but still no luck. The backup device type is disk
Kindly help on the same
Regards,
Anand

Hello Vedival.
I am getting exact same error.
We are using Tivoli with BRTOOLS and no RMAN at all..not sure why at the end of Backup its executing "'SHELL=/bin/sh /oracle/QAS/102_64/bin/rman nocatalog'" command.
I will appreciate your help.
Thanks
Laxmichand.
BR0530I Cataloging backups of all database files...
BR0278E Command output of 'SHELL=/bin/sh /oracle/QAS/102_64/bin/rman nocatalog':
Recovery Manager: Release 10.2.0.2.0 - Production on Fri Oct 8 01:23:12 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
RMAN>
RMAN> connect target *
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-04002: ocipi failed, ORA 1
RMAN> *end-of-file*
RMAN>
host command complete
RMAN> 2> 3> 4> 5> 6> 7> 8> 9> 10> 11> 12> 13> 14> 15> 16> 17> 18> 19> 20> 21> 22> 23> 24> 25> 26> 27> 28> 29> 30>
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of catalog command at 10/08/2010 01:23:15
RMAN-06171: not connected to target database
RMAN>
Recovery Manager complete.
BR0280I BRBACKUP time stamp: 2010-10-08 01.23.15
BR0279E Return code from 'SHELL=/bin/sh /oracle/QAS/102_64/bin/rman nocatalog': 1
BR0536E RMAN call for database instance QAS failed
BR0280I BRBACKUP time stamp: 2010-10-08 01.23.15
BR0532E Cataloging backups of all database files failed
BR0280I BRBACKUP time stamp: 2010-10-08 01.23.40
BR0317I 'Alter database end backup' successful
BR0056I End of database backup: beehfpbh.fnf 2010-10-08 01.23.15
BR0280I BRBACKUP time stamp: 2010-10-08 01.23.41

ORA-00245: control file backup failed; target is likely on a local file sys

Hello,
our RAC (Linux, 11.2.0.3.0) is rather new and we are still on gaining experiences with that system...
When starting the backup with RMAN we are getting the following error:
Starting Control File and SPFILE Autobackup at 04-JUL-12
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of Control File and SPFILE Autobackup command on ORA_DISK_1 channel at 07/04/2012 16:41:48
ORA-00245: control file backup failed; target is likely on a local file system
The reason for the error is clear ORA-00245 - in a RAC environment the location of the Snapshot Controlfile must be on a shared location.
When executing the RMAN command "show all" on each node, we are getting
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11.2.0.3/db/dbs/snapcf_PROD021.f'; # default
for node #1
and
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11.2.0.3/db/dbs/snapcf_PROD022.f'; # default
for node #2
When using a shared location for the Snapshot Controlfile do we still need to setup 2 different names for that file?
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/<shared location>/snapcf_PROD021.f'; # default
for node #1 and
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/<shared location>/snapcf_PROD022.f'; # default
for node #2
Or should we configure just one Snapshot Controlfile?
The RMAN setup for "CONFIGURE SNAPSHOT CONTROLFILE NAME TO..." must be changed on both nodes - correct?
Hopefully my question is clear enough - any help will be appreciated.
Rgds
JH
Edited by: VivaLaVida on 05.07.2012 11:41

No, it must be configured on a shared storage:Not really required, i've RAC setup and snapshot is configured on local storage.
Configuring the RMAN Snapshot Control File Location
The snapshot control file is a copy of a database control file created in an operating system-specific location by Recovery Manager. RMAN creates the snapshot control file so that it has a consistent version of a control file to use when either resynchronizing the recovery catalog or backing up the control file. In Oracle RAC, the snapshot control file is only needed on the nodes on which RMAN performs backups; the snapshot control file does not need to be globally available to all instances in an Oracle RAC environment.
See below from doc.
http://docs.oracle.com/cd/B28359_01/rac.111/b28254/rman.htm#i455026

Ora - 01536 Tablespace Quota

I am getting an error
ORA - 01536 : Space Quota exceeded for tablespace 'Tablespacename';
I have tried options like
alter user <username> quota unlimited on <Tablespacename>;
Grant resource to <username>;
I am still getting the same error
Please can any one help me
Lakshmi Nar

Perhaps you are giving quota in the wrong tablespace. Can you post the complete error ?
Perhaps that user is trying to stored objects in another tablespace different than its default tablespace.
Joel Pérez

Regarding ORA-00001: unique constraint violation error

Hi ,
This is Venkat. I am new to OWB.
When I run the mapping I am getting the ORA-00001: unique constraint violation error.
My loading type is Update/Insert.
My target table Primarykey is combination of 3 keys.
Please give me the suggestions. It is very urgent.
Thanks,
Venkat

1) If you can disable/drop the indexes on the table, you can load the data and then do a SQL query grouping by the PK/UI to show which rows have a count > 1 i.e. the duplicates.
2) If you can't alter the target table, perhaps create a dummy copy of the table without pk/indexes and load to that and then do above query.
3) Run the mapping via the debugger and set a breakpoint just before your target table and examine the data to see if you can spot the duplicates.
4) Put a deduplicator into the mapping (just before target table), this may allow you to load data but doesn't solve the real problem as to why you have duplicates.
Si

ORA-01122: database file 58 failed verification check

Hi All,
I have lost one of my datafile while moving them from 1 drive to another. I am getting the following error while trying to start the database:
ORA-01122: database file 58 failed verification check
ORA-01110: data file 58: 'G:\ORACLE\R3E\SAPDATA7\R3E700_25\R3E700.DATA25'
ORA-01251: Unknown File Header Version read for file number 58
Please suggest what can be done to correct the error. Also I don't have a backup.
Suman

- open http://service.sap.com/notes
- enter "ORA-01251"
- you will find Note 696141 - Composite SAP Note: ORA-01122
and that section:
10. ORA-01251: Unknown File Header Version read for file number <file_id>
Reason: The file header cannot be correctly read.
Solution: If you use Oracle 9.2 on WINDOWS and if you already installed the database with Oracle 7.2 or lower, see Note 636466.
Otherwise: Restore/recovery
Markus

ORA-01122: database file 30 failed verification check

SQL*Plus: Release 10.1.0.4.2 - Production on Wed Feb 13 20:33:13 2008
Copyright (c) 1982, 2005, Oracle. All rights reserved.
when starting the DB for 10gAS get following error, db is started but cannot sign in
SQL> SQL> Connected.
SQL> ALTER DATABASE open
ERROR at line 1:
ORA-01122: database file 30 failed verification check
ORA-01110: data file 30: 'D:\ORACLE\ORADATA\PRT\APPS003_A.DBF'
ORA-01203: wrong incarnation of this file - wrong creation SCN
Disconnected from Oracle Database 10g Enterprise Edition Release 10.1.0.4.2 - Production
With the Partitioning, OLAP and Data Mining options

You have a mismatch in the control file and data file scn numbers. What was done before the database was getting started? I once saw this error when some one moved one file from another munt point to another and there was no rename give to the control file and the control file got no idea which is this new file and where it had come from?
Try finding the control file which is of the same backup as of this datafile.
Aman....

ORA-28547: connection to server failed, probable Oracle Net admin error

Hi Gurus
I can't get the gateway to work? I'm running on AIX. Any suggestions are appreciated.
listener.ora
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1522))
# (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1522))
SID_LIST_LISTENER=
(SID_LIST=
(SID_DESC=
(SID_NAME=dg4msql)
(ORACLE_HOME=/oracle/rcsr/base/product/11.2.0/gateway)
(PROGRAM=dg4msql)
tnsnames.ora
dg4msql =
(DESCRIPTION=
(ADDRESS=(PROTOCOL=tcp)(HOST=localhost)(PORT=1522))
(CONNECT_DATA=(SID=dg4msql))
(HS=OK)
sqlnet.ora
SQL_AUTHENTICATION_SERVICES = (NONE)
NAMES.DIRECTORY_PATH= (TNSNAMES)
ADR_BASE = /oracle/rcsr/base
initdg4msql.ora
HS_FDS_CONNECT_INFO=142.178.205.42:1433//komodo
# alternate connect format is hostname/serverinstance/databasename
HS_FDS_TRACE_LEVEL=debug
HS_FDS_RECOVERY_ACCOUNT=RECOVER
HS_FDS_RECOVERY_PWD=RECOVER
$ lsnrctl status
LSNRCTL for IBM/AIX RISC System/6000: Version 11.2.0.1.0 - Production on 03-MAY-2013 13:48:01
Copyright (c) 1991, 2009, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=localhost)(PORT=1522)))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for IBM/AIX RISC System/6000: Version 11.2.0.1.0 - Production
Start Date 03-MAY-2013 13:38:14
Uptime 0 days 0 hr. 9 min. 47 sec
Trace Level off
Security ON: Local OS Authentication
SNMP ON
Listener Parameter File /oracle/rcsr/base/product/11.2.0/gateway/network/admin/listener.ora
Listener Log File /oracle/rcsr/base/diag/tnslsnr/abe-rcsr-01/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=1522)))
Services Summary...
Service "dg4msql" has 1 instance(s).
Instance "dg4msql", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
$ tnsping dg4msql
TNS Ping Utility for IBM/AIX RISC System/6000: Version 11.2.0.1.0 - Production on 03-MAY-2013 13:48:53
Copyright (c) 1997, 2009, Oracle. All rights reserved.
Used parameter files:
/oracle/rcsr/base/product/11.2.0/gateway/network/admin/sqlnet.ora
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=localhost)(PORT=1522)) (CONNECT_DATA=(SID=dg4msql)) (HS=OK))
OK (0 msec)
$ sqlplus aa/aa@dg4msql
SQL*Plus: Release 11.2.0.1.0 Production on Fri May 3 13:49:52 2013
Copyright (c) 1982, 2009, Oracle. All rights reserved.
ERROR:
ORA-28547: connection to server failed, probable Oracle Net admin error

You can't directly use the gateway - you can only access a gateway using a database link.
So this won't work:
$ sqlplus aa/aa@dg4msql
You need to connect to your Oracle database (for example as sysdba) and create a (public) database link:
create [public] database link dg4msql connect to "<MS SQl Server username! identified by "<MS SQl Server password>" using 'dg4msql;
Once you create the database link you can now access the MS SQl Server tables:
select * from "your MS SQL Server table"@dg4msql;

ORA-30027:Undo quota violation failed to get 92 (Bytes)

Similar Messages

Maybe you are looking for