integration oracle9 for Data Protector5

[방가워]

Data Protector5에 oracle9을 integration 하고자 합니다.

아시는 분 알려주시면 감사하겠습니다.

매뉴얼을 보고 했는데 오라클의 rman 대한 개념이 없어서 그런지 잘안되네요.....



현재 oracle9와 data protector5을 기본설치한 상태입니다.



rman을 config 하고 integration해야 하는지 아니면 매뉴얼에 있는

그대로 해도 되는지....^^;;

꾸뻑 정답 알려주시는분께 후사 하겠습니다.



그리고 다음 메시지을 ORACLE rman에서 뿌려 줍니다.

=============== ERROR MESSAGE STACK FOLLOWS ===============

[Joseph]

Rman은 보통 여러개의 DB를 가지고 있을 경우 오라클에서 백업과 복구 관리를 위해서 사용하는 또다른 DB죠.

그래서 예전에 한번 공부하면서 Rman을 Setting한 적이 있구..

그 이후로는 전무하네요^^.

제 생각에는 rman를 먼저 config하고 DP5에서 integration해야 할 것 같네요.

그리고 에러 메세지의 내용이 없네요..



아래 포럼 정보는 참고하세요..^^



-metalink.oracle.com에서-

Rman resync job fails against Oracle 9i database



A resync job between the RMAN recovery catalog and an Oracle 9i database, via an OEM backup configuration, only seems to work if my preferred credentials are set AS SYSDBA.

If my preferred credentials are set AS NORMAL and even if I override the preferred credentials in the definition of the backup configuration the job fails, because it's not able to connect to the target database. The same job works fine for my Oracle 8i databases.



Example output:

-----------------

Recovery Manager: Release 9.2.0.3.0 - Production



Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.



RMAN>

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

ORA-01031: insufficient privileges



RMAN>

connected to recovery catalog database



RMAN>

RMAN> resync catalog;

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-03002: failure of resync command at 01/06/2004 10:55:40

RMAN-06171: not connected to target database



RMAN> **end-of-file**



RMAN>



Recovery Manager complete.



child process exited abnormally



Regards, Jan











--------------------------------------------------------------------------------



보낸 사람: Oracle, Nahed Majzoub 08-Jan-04 21:39

제목: Re : Rman resync job fails against Oracle 9i database





anytime you connect to the targert db you need sysdba, what do you mean by you do not need sysdba in 8i? Maybe the user you are using has already been granted this role



Thank you for using our forum

Nahed Majzoub







--------------------------------------------------------------------------------



보낸 사람: Jan Jacobs 09-Jan-04 10:29

제목: Re : Rman resync job fails against Oracle 9i database





Following your reply, Nahed, I did some additional tests and as you stated the SYSTEM user needed SYSDBA privilege on the 9i database. I granted this privilege to this user (as already done by a collegue of mine for the 8i databases) and everything worked fine.



Even if the preferred credentials are set as NORMAL, the resync job works fine.



FYI: The override option in the "Backup configuration" doesn't seem to work. Even if I try to override the preferred credentials with the user SYS the job fails with the above error. The preferred credentials use in this case a user without SYSDBA privilege.



However, for me this problem is solved. I granted SYSTEM the sysdba privilege and I use the preferred credentials in the backup configuration.



Thanks for your assistance.

Jan











--------------------------------------------------------------------------------



보낸 사람: Oracle, Nahed Majzoub 09-Jan-04 17:16

제목: Re : Re : Rman resync job fails against Oracle 9i database





hello



Glad that your issue is solved. The "override preferred credential" should work fine. I am not sure why SYS is not working for you as a db user. When you do override the job fails at least we know that the new user is picked up and not the old one (As specicified in the preferred credentials). Try submitting the same backup job from sqlplus as SYS and see if this does succeeds... Not sure why this will fail but we can track it down if this becomes an issue. You can actually try creating another user but SYS and grant it the sysdba privileges and run it as to override the preferred credentials and see if that works from oem







Thank you for using our forum

Nahed Majzoub