ORA-01017 after changing SYSTEM password

[tobias_ptz]

Hello everybody!

Little introduction:

we have a running ERP ECC 6.0 system.

In this system we've changed the password of the SYSTEM user. (from 'manager' to 'SIDmypw5')

All things working fine, no problem or failurs are occured. DB13 (CheckDB runs out of errors)

Now we wanna setup a oracle standby database for this system.

This installation way worked for other systems before, but in these systems the user SYSTEM has 'manager' as his password!

- do full offline backup, create standby controlfile, restore backup on the standby machine and change controlfiles, edit tnsnames.ora/SIDinit.sap/scripts and so on. Even all things to get a working standby system!

After all, we want to copy the next Redo-Logfiles after the offline backup, but we run into an error:

The logs were copied, but after doing this 5 times, the user SYSTEM is locked.

E:\oracle\HP3\102\database\Scripts>brarchive -s -c -d disk -w
BR0002I BRARCHIVE 7.00 (42)
BR0006I Start of offline redo log processing: aedpyctg.sve 2010-07-08 12.39.08
BR0484I BRARCHIVE log file: H:\oracle\SID\saparch\aedpyctg.sve
BR0280I BRARCHIVE time stamp: 2010-07-08 12.39.08
BR0301W SQL error -1017 at location BrDbConnect-2, SQL statement:
'CONNECT system/*******'
ORA-01017: invalid username/password; logon denied
BR0310W Connect to database instance SID failed

On the other side (standby) we wanna apply the next Redo-Logs with a delay of 8 hours (480 min):

C:\Documents and Settings\SIDadm>brarchive -n 2770+1000 -m 480
BR0002I BRARCHIVE 7.00 (42)
BR0006I Start of offline redo log processing: aedpppdp.sve 2010-07-06 19.02.25
BR0484I BRARCHIVE log file: H:\oracle\SID\saparch\aedpppdp.sve
BR0280I BRARCHIVE time stamp: 2010-07-06 19.02.25
BR0301W SQL error -1017 at location BrDbConnect-2, SQL statement:
'CONNECT system/*******@SID'
ORA-01017: invalid username/password; logon denied
BR0310W Connect to database instance SID/PRIMARY failed

If we do this way with the SYSTEM user and password 'manager', all this works fine!

We've searched SDN and SMP, but didn't found a solution.

Why is BRTOOLS trying connect to database with the old password?

Where can i give BRTOOLS the new password?

We have change the SYSTEM password with: ALTER USER SYSTEM IDENTIFIED BY <password>; and over the BRTOOLS itself.

Is there any thing we've got miss to do?

OS: Win2k3 / Win2k8 (with both OS)

DB: Oracle 10.2.0.2 / Oracle 10.2.0.4 (with both RDBMS)

SAP: ERP ECC 6.0

Anyone any idea?

Thanks for every help.

Tobias

[lbreddemann · Accepted solution]

> We've searched SDN and SMP, but didn't found a solution.

>

> Why is BRTOOLS trying connect to database with the old password?

> Where can i give BRTOOLS the new password?

>

> We have change the SYSTEM password with: ALTER USER SYSTEM IDENTIFIED BY <password>; and over the BRTOOLS itself.

>

> Is there any thing we've got miss to do?

How about just using the -u / logon?

Make the SAPService<SID> and <SID>ADM (on Windows level!) members of ORA_DBA and ORA_OPER group and then you can easily logon via OS-Authentication.

No need to provide a plain text password or to leave the standard password in place.

The brtools call would be like:

brbackup -u / ...

regards,

Lars

[tobias_ptz · Accepted solution]

Damn it!

That's all? - Yes it is!!! arg

Well, thanks for all your replies!

Tobias

ps. maybe one question: what did you mean with the oracle password file?

Is it a clear text file, which includes the password for the SYSTEM user?

This it not really safety, isn't it?

Thanks!

[Former Member · Accepted solution]

Hi Tobias,

The Oracle password file is an encrypted file that allows remote access to the standby database from the primary database. You need to have the same file on your standby system as is on your primary system in order to be able to use the Oracle Dataguard Broker. Looking more closely at your original post, I don't think you are using the Dataguard Broker, so it is probably not a requirement in your case.

Cheers, Barry.

[Former Member]

Hi Tobias,

you need to use the option -u of the br* tools as follows:

brarchive -u system/<new pwd> -s -c -d disk -w

&

brarchive -u system/<new pwd> -n 2770+1000 -m 480

In general, if the password of user SYSTEM is not the default, you must use the option "-u system/<new pwd>".

Regards,

Constantina

[Former Member]

Hi,

Did you copy the Oracle password file from the Primary system to the standby system ? If not, then that is probably why you are getting the authorisation error.