Author: mac

ORA-01552 and ORA-00942 Rollback Segments Offline Received During Installation

如果自己搞不定可以找诗檀软件专业ORACLE数据库修复团队成员帮您恢复! 诗檀软件专业数据库修复团队服务热线： 13764045638 QQ号:47079569 邮箱：[email protected] 症状这是安装ASAP时可能发生的一个致命错误。出现此错误是因为，当创建ASAP的Oracle数据库时，其回滚段默认是离线的。Oracle系统账户要求这些回滚段必须是在线的。 ASAP安装将不得不重新进行。这些错误是在ASAP安装文件 CreateDatabase.log中发现的: …<cut>… Convert ‘SARM’ DB index tablespace to [SARM_INDEX] Populating static database definitions … Populating database definition for CTRL (control.sql) Sequence created. ‘Loading tables/IDENTITY.i’ CHECK (opt5_type = null or opt5_type like ‘-_’), * ERROR at line 18: ORA-01552: cannot use system rollback…

March 23, 2013
Oracle ORA-01552 While Creating Undo Tablespace

如果自己搞不定可以找诗檀软件专业ORACLE数据库修复团队成员帮您恢复! 诗檀软件专业数据库修复团队服务热线： 13764045638 QQ号:47079569 邮箱：[email protected] oerr ora 1552 01552, 00000, “cannot use system rollback segment for non-system tablespace ‘%s'” // *Cause: Tried to use the system rollback segment for operations involving // non-system tablespace. If this is a clone database then this will // happen when attempting any data modification outside of…

March 23, 2013
SARM Server Terminates and ORA-25408 Appears When RAC Switches The Database Due to Failover

如果自己搞不定可以找诗檀软件专业ORACLE数据库修复团队成员帮您恢复! 诗檀软件专业数据库修复团队服务热线： 13764045638 QQ号:47079569 邮箱：[email protected] 症状当RAC因故障转移切换数据库时，SARM服务器终止，且在SARM/NEP诊断文件上出现ORA-25408错误。 SARM diag: >> 131654.052:36:PROG:ASC_cprpcexec() :1424:control/libasc/ctlib.c RPC SSP_ne_log failed. Error code:[25408] >> 131654.052:39:PROG:checkerr_returning_errcod:1707:control/libasc/ocilib.c Error – ORA-25408: can not safely replay call errcode[25408] >> 131654.053:35:PROG:checkerr_returning_errcod:1707:control/libasc/ocilib.c Error – ORA-25408: can not safely replay call errcode[25408] >> 131654.053:47:PROG:ASC_cprpcexec() :1424:control/libasc/ctlib.c RPC SSP_ne_log…

March 23, 2013
ORA-03113 ASAP Orders Are Getting Stuck Frequently With RPC Failure errcode[3113] in NEP

如果自己搞不定可以找诗檀软件专业ORACLE数据库修复团队成员帮您恢复! 诗檀软件专业数据库修复团队服务热线： 13764045638 QQ号:47079569 邮箱：[email protected] 症状 ASAP命令卡住。这要求用户停下来，然后启动ASAP来处理命令asap_utils -d 7 显示 “Connecting not available”。ASAP重启后, 显示 “Available”。 NEP 诊断文件显示以下错误: >> 192407.160:51: LOW:ASC_cppalloc :348 :control/libcontrol/ctlib.c Successfully obtained a Session from the Pool >> 192407.160:51: LOW:ASC_cprpcexec_nobind() :2777:control/libasc/ctlib.c Executing RPC [SSP_nep_tech]. Retry Count [0] >> 192950.595:51:SANE:ORACLE ERROR :1227:control/libasc/ocilib.c — ORACLE error OCIStmtExecute >> 192950.595:51:PROG:checkerr_returning_errcod:1658:control/libasc/ocilib.c Error – ORA-03113: end-of-file…

March 23, 2013
Oracle ORA-1242, ORA-1122, ORA-1110 & ORA-1208 Errors Occurring Intermittently

如果自己搞不定可以找诗檀软件专业ORACLE数据库修复团队成员帮您恢复! 诗檀软件专业数据库修复团队服务热线： 13764045638 QQ号:47079569 邮箱：[email protected] 症状你遇到下列在警报日志中周期性出现的错误: ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode ORA-01122: database file %d failed verification check ORA-01110: data file %d: ‘%s’ ORA-01208: data file is an old version – not accessing current version 指定的数据文件保持在线和可用，因此不存在明显的损坏，在底层磁盘上不会出现I/O错误。原因当在NOARCHIVELOG模式下运行数据库时，由于大量的磁盘I/O使用，导致 I/O性能受影响，可能会出现这种问题。例如，重做日志切换太频繁，因此用最新的检查点scn更新控制文件,但在用相同检查点scn信息更新数据文件头之前，数据文件就被访问，因此Oracle报告ORA-1208错误为：数据文件比控制文件中所列的更早。随后数据文件头被更新，因此可被正常访问，不会发生任何损坏。解决方案这里的解决方案是解决底层磁盘I/O的性能问题。如果由于重做日志切换太频繁发生该问题，也就是相隔几秒，请参考Note:147468.1关于如何调整检查点操作，尤其是section 4关于正确的重做日志文件大小(参见Note:1038851.6)来解决该问题。

March 23, 2013
Data File Suffered Media Failure: Database In Noarchivelog Mode Ora-01242

如果自己搞不定可以找诗檀软件专业ORACLE数据库修复团队成员帮您恢复! 诗檀软件专业数据库修复团队服务热线： 13764045638 QQ号:47079569 邮箱：[email protected] 症状 ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode ORA-01122: database file 3 failed verification check ORA-01110: data file 3: ‘D:\BODBF\USER02BO.DBF’ ORA-01208: data file is an old version – not accessing current version error 1242 detected in background process Errors in file d:\bodbf\trace\bdump\bodbLGWR.TRC:…

March 23, 2013
Oracle Database Instance Crashes If ASM Failgroup Is Overwritten By /dev/zero

如果自己搞不定可以找诗檀软件专业ORACLE数据库修复团队成员帮您恢复! 诗檀软件专业数据库修复团队服务热线： 13764045638 QQ号:47079569 邮箱：[email protected] [oracle@ocm_rac01 ~]$ oerr ora 27091 27091, 00000, “unable to queue I/O” // *Cause: read/write/readv/writev system call returned error, additional // information indicates starting block number of I/O // *Action: check errno [oracle@ocm_rac01 ~]$ oerr ora 27072 27072, 00000, “File I/O error” // *Cause: read/write/readv/writev system call returned…

March 23, 2013
Oracle ODM issues for Solaris

如果自己搞不定可以找诗檀软件专业ORACLE数据库修复团队成员帮您恢复! 诗檀软件专业数据库修复团队服务热线： 13764045638 QQ号:47079569 邮箱：[email protected] oerr ora 1243 01243, 00000, “system tablespace file suffered media failure” // *Cause: A system tablespace file was detected as inaccessible due to // media failure. // *Action: Restore accessibility to the file mentioned in the error stack // and restart the instance. 症状在操作系统从Solaris 8 迁移到…

March 23, 2013
Oracle ora-1245 Workaround for Flashback Database fails with ORA-38753 ORA-01110

如果自己搞不定可以找诗檀软件专业ORACLE数据库修复团队成员帮您恢复! 诗檀软件专业数据库修复团队服务热线： 13764045638 QQ号:47079569 邮箱：[email protected] oerr ora 1245 01245, 00000, “offline file %s will be lost if RESETLOGS is done” // *Cause: Attempting to do an OPEN RESETLOGS with a file that will be lost // because it is offline. The file was not taken offline with the // FOR DROP option.…

March 23, 2013
Oracle Error Logging into Expedition Administration: “Cannot Connect to Administration Database ORA-1256”

如果自己搞不定可以找诗檀软件专业ORACLE数据库修复团队成员帮您恢复! 诗檀软件专业数据库修复团队服务热线： 13764045638 QQ号:47079569 邮箱：[email protected] 症状错误记录到远程管理日志中: “Cannot Connect to Administration Database ORA-1256” 原因通常会指向管理数据库位置的远征注册表项丢失。解决方案启动注册表编辑器, Start->Run and type regedit. 浏览到 HKEY_CURRENT_USER\Software\Primavera\Expedition\Database 检查看是否有一个叫做Servername的字符串值。如有，确保该值是正确的Expedition Oracle服务器名。如没有，继续进行以下操作Edit->New->String Value。输入 ‘Servername’ 找到该值的名称，点 OK。双击new entry 并输入正确的Expedition Oracle 服务器名。关闭注册表，启动Expedition.

March 23, 2013