Oralce ASM 测试
[Thread-13] [2:4:59:548] [SQLEngine.spoolOff:1811] Setting spool off = /opt/oracle/product/10.2.0/db_1/cfgtoollogs/dbca/ORCL
/CloneRmanRestore.log
oracle.sysman.assistants.util.sqlEngine.SQLFatalErrorException: ORA-19624: ????, ???????
ORA-19870: ????? /opt/oracle/product/10.2.0/db_1/assistants/dbca/templates/Seed_Database.dfb ???
ORA-19504: ??????"+DATA1"
ORA-17502: ksfdcre: 4 ?????? +DATA1
ORA-15001: ??? "DATA1" ????????
ORA-15055: ????? ASM ??
ORA-01031: insufficient privileges
ORA-06512: ? "SYS.X$DBMS_BACKUP_RESTORE", line 5149
ORA-06512: ? line 40
错误详细说明：
19624, 00000, "operation failed, retry possible"
// *Cause: A backup, restore or image copy operation failed with an I/O
// error. If the source of the I/O error can be corrected, then
// the operation may be retried.
// *Action: This message is used by recovery manager to decide whether or not
// to retry the operation.
19870, 00000, "error reading backup piece %s"
// *Cause: This error should be followed by other errors indicating
// the cause of the problem.
// *Action: See other errors actions.
//
// Do not use message 19871; it is used by RMAN client for testing previous
// resync time when using backup/standby control file.
19504, 00000, "failed to create file \"%s\""
// *Cause: call to create file returned an error
// *Action: check additional messages, check access permissions
17502, 00000, "ksfdcre:%s Failed to create file %s"
// *Cause: file creation failed due to either insufficient OS permission or
// the file already exists
// *Action: check additional error messages
15001, 00000, "diskgroup \"%s\" does not exist or is not mounted"
// *Cause: An operation failed because the diskgroup specified does not
// exist or is not mounted by the current ASM instance.
// *Action: Verify that the diskgroup name used is valid, that the
// diskgroup exists, and that the diskgroup is mounted by
// the current ASM instance.
//
15055, 00000, "unable to connect to ASM instance"
// *Cause: When accessing a diskgroup for the first time, the database
// was unable to connect to the required ASM instance.
// *Action: Check the additional error messages. May need to configure
// correct ASM sid or make sure the database instance has OS
// privileges for ASM SYSDBA.
//
01031, 00000, "insufficient privileges"
// *Cause: An attempt was made to change the current username or password
// without the appropriate privilege. This error also occurs if
// attempting to install a database without the necessary operating
// system privileges.
// When Trusted Oracle is configure in DBMS MAC, this error may occur
// if the user was granted the necessary privilege at a higher label
// than the current login.
// *Action: Ask the database administrator to perform the operation or grant
// the required privileges.
// For Trusted Oracle users getting this error although granted the
// the appropriate privilege at a higher label, ask the database
// administrator to regrant the privilege at the appropriate label.
06512, 00000, "at %sline %s"
// *Cause: Backtrace message as the stack is unwound by unhandled
// exceptions.
// *Action: Fix the problem causing the exception or write an exception
// handler for this condition. Or you may need to contact your
// application administrator or DBA.
06512, 00000, "at %sline %s"
// *Cause: Backtrace message as the stack is unwound by unhandled
// exceptions.
// *Action: Fix the problem causing the exception or write an exception
// handler for this condition. Or you may need to contact your
// application administrator or DBA.
