1

Topic: Basis recovery 11g

Kind time, days;
So happens that flooded server, it is natural there where went  too not to pull out, there was a hard disk with the basis which was naturally incorrectly ungeared. Now I try to lift it on other computer, in general I do the following, I create service I change init.ora for new ways, but it is visible it insufficiently.
> oradim-new-sid temp-pfile c:\oracle\temp\init.ora
> set ORACLE_SID=temp
> sqlplus "/ AS SYSDBA"
On this line an error, checked up all ways files all are present
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
Process identifier: 0
The session identifier: 0 Ordinal value: 0
As I suppose, there is an error to corrections init.ora, stick with a nose what not so I do.
[spoiler ]
##############################################################################
# Copyright (c) 1991, 2001, 2002 by Oracle Corporation
##############################################################################
###########################################
# Cache and I/O
###########################################
db_block_size=8192
###########################################
# Cursors and Library Cache
###########################################
open_cursors=300
###########################################
# Database Identification
###########################################
db_domain = ""
db_name=DBDIM
###########################################
# File Configuration
###########################################
control_files = ("d:\Database\DBDIM\control01.ctl", "d:\app\administrator\flash_recovery_area\DBDIM\control02.ctl")
db_recovery_file_dest=d:\app\administrator\flash_recovery_area
db_recovery_file_dest_size=4102029312
###########################################
# Miscellaneous
###########################################
compatible=11.2.0.0.0
diagnostic_dest=d:\app\administrator
memory_target=4214226944
###########################################
# NLS
###########################################
nls_language = "RUSSIAN"
nls_territory = "RUSSIA"
###########################################
# Processes and Sessions
###########################################
processes=300
sessions=335
###########################################
# Security and Auditing
###########################################
audit_file_dest=d:\app\administrator\admin\DBDIM\adump
audit_trail=db
remote_login_passwordfile=EXCLUSIVE
###########################################
# Shared Server
###########################################
dispatchers = "(PROTOCOL=TCP) (SERVICE=DBDIMXDB)"
###########################################
# System Managed Undo and Rollback Segments
###########################################
undo_tablespace=UNDOTBS1
[/spoiler]
Difference only in operative storage...
Thanks.

2

Re: Basis recovery 11g

Naturally  I fulfill so where it is stored itself spfile:
oradim-new-sid DBDIM-pfile D:\Database\DBDIM\init.ora

3

Re: Basis recovery 11g

alert.log

4

Re: Basis recovery 11g

basis Cloning .

5

Re: Basis recovery 11g

In general it was possible to initialize all and the basis rose, but there was still an error:
Errors in file c:\database\diag\rdbms\dbdim\dbdim\trace\tdpra_cjq0_2344.trc:
ORA-00604: an error at the recursive SQL-level 1
ORA-06544: PL/SQL: ., arguments: [56327], [], [], [], [], [], [], []
ORA-06553: PLS-801: . [56327]
Also it is impossible ...

6

Re: Basis recovery 11g

kiv-1980;
http://www.sql.ru/forum/1292574/nuzhna- … azy?hl=ora 00604

7

Re: Basis recovery 11g

Relic Hunter;
Well and what for to me this link.
Enough was to launch in migrated, all earned, all flied up!
[spoiler]
ORA-06553: PLS-801: internal error [56327]
I now have a datafile from windows 2008 (X64) cold standby out above, now I put him to restore to win7 (X86) machine, the database version is 11R2, restored startup is fine, but the connection and execution sql statement will be reported when:
SQL> conn user / userpassword
ERROR:
ORA-00604: recursive SQL level 1 error
ORA-06553: PLS-801: internal error [56327]
ORA-06553: PLS-801: internal error [56327]
An error occurred while accessing the package DBMS_APPLICATION_INFO
Is connected.
SQL>
---------
Is there any way to solve this problem.
Reply:
1, Shutdown immediate
2, startup migrate
Note: startup migrate expressed downgrade in 9i, regardless of the upgrade / downgrade databases are startup migrate;
10g parameters added after upgrade, the upgrade can be directly used startup upgrade, downgrade still a startup migrate.
3, $ ORACLE_HOME / rdbms / admin / utlirp.sql;
4, Shutdown immediate
5, Startup
6, $ ORACLE_HOME / rdbms / admin / utlrp.sql;
7, Shutdown immediate
8, Startup
http://www.itpub.net/thread-1117964-1-1.html
Try it, in theory, no problem
[/spoiler]

8

Re: Basis recovery 11g

In general I early was delighted, the basis is connected, users sys, system are accessible, the roles created by me and users too are accessible, and here tables, , procedures and other, remained are inaccessible. The same error took off all. For scripts refused to work, producing the next error.
It was necessary to dig further, found the following decision which is fulfilled successfully without errors, while;
The way should specify straight lines to scripts which start to process already correctly labels and to put them in order.
SQL> shutdown immediate;
SQL> startup upgrade;
SQL> @C:\OraBase\product\11.2.0\dbhome_1\RDBMS\ADMIN\utlirp;
SQL> shutdown immediate;
SQL> startup;
SQL> @@ C:\OraBase\product\11.2.0\dbhome_1\RDBMS\ADMIN\utlrp;
SQL> shutdown immediate;
SQL> startup;
Here actually all also earned, the difference was in   as I raised on , actually and did not pay attention on  32, and the basis was 64. And did not assume that there will be such problem.

9

Re: Basis recovery 11g

kiv-1980;

Vadim Lejnin wrote:

YuriYurich;
Recover from backup
At you garbage instead of basis
That that happened - analog backup bases on hot

10

Re: Basis recovery 11g

Relic Hunter;
What garbage? Completely the efficient basis, any incorrect unit and loss, upon there was a switch-off.
Now lifted the last file temp01.dbf, acted in film , all labels earned and were initialized on 100 %.
In  any error.
With the link resulted by you, my situation, has not something in common.
The basis earned! The question is removed.

11

Re: Basis recovery 11g

wrote:

it is normal after such wonderful recovery it is recommended to alter basis with . Inside there can be the strange things which get out later - at an upgrade or  patches, switching-on any OLAP and .

Can still recommend .  to do and  to deliver?

12

Re: Basis recovery 11g

The basis was twisted on two SSD which stood a mirror, there where were  there was no mirror though most likely and it did not rescue.
And so both SSD in Online (100 % live, there water did not get, it is simple because they small), but the system departed with  (such I could not assume, force-majeur). And I simply copied this basis and lifted on  to pull out the data, the first problem arose with a role ora_dba for the domain user, in the rights is, and it all the same did not take in sql + as sysdba, underwent treatment the normal user with the rights ora_dba, then after location change, there was the recursive error because of a difference 64 - 32, migrated and upgrated together with alteration and check of tables, fulfilled correctly, all spoiled a little temp01.dbf (because of it a part of tables were with errors and it is natural  did not act in film), but after alter, steams shutdown - startup, it too rose. Everything after that all labels, procedures, functions and other, without a uniform error with all data were preempted in . The first sight and that that had time to walk, like all the data is correct.
Probably though here, carried a little...