DB13 jobs doesn't work anymore

[Former Member]

Hi all,

we have the folowing problem :

our D01(it is an ERP-system) was separate installed on two

different servers (application server (was srv056) and database(srd455)

were separate installed). Three weeks ago we have moved them both(the

application server and the database) on one standalone server - srd433.

Since then we cannot execute different programs in transaction

DB13 - "check database","cleanup logs", "verify db" etc doesnu2019t work

anymore. The log we send is the entire log we have:

___

Job started

Step 001 started (program RSDBAJOB, variant &0000000000027, user ID

BASIS_ADM)

Execute logical command BRCONNECT On host srd455

Parameters: -u / -jid CHECK20091112121329 -c -f check

No vendor specified

No vendor specified

No vendor specified

No vendor specified

SXPG_STEP_COMMAND_START: SXPG_STEP_XPG_START returned: 1.003

SXPG_COMMAND_EXECUTE(LONG)

COMMANDNAME = BRCONNECT

OPERATINGSYSTEM = ANYOS

TARGETSYSTEM = srd455

DESTINATION =

SXPG_COMMAND_EXECUTE failed for BRCONNECT - Reason:

program_start_error:For More Information, See SYS

Job cancelled after system exception ERROR_MESSAGE

___

We have noticed in the log, that the BRCONNECT tried to connect with

the srd455, which is the old (and false) server - the new one is

srd433!

We have noticed also, that in transaction SM59 there are two

automatically generated connections:

- SAPXPG_DBDEST_SRD433 (the correct one)

- SAPXPG_DBDEST_SRD455 (the false one).

We have tried to delete the false one many times, but every time we

executed a program in transaction DB13, the false one was generated

again.

Please help us, thank you in advance for your efforts!

Alex

[Former Member]

Thanks a lot !!!

[Former Member]

Hi Aleksandar

We have same problem in our ERP System. Our DBA migrate Oracle databese in other system. They change server name and virtual cluster name. Now when i run any task the older name appear and don't find whats is a problema. I have same problema that you say here ind like to know how you solve your problema. Excuse my bad english .

Best Regards

Wilson Salazar

[anindya_bose]

Hi Alex

Please check sap note Note 446172

Is the connection test for SAPXPG_DBDEST_SRD433 RFC is fine? What is the value for parameter SAPDBHOST?

Regards

Anindya

Edited by: Anindya Bose on Nov 25, 2009 5:25 PM

[Former Member]

Hello Anindya,

I have read the note 446172 already, but didn't find the solution for my problem.

Yes - the connection test for SAPXPG_DBDEST_SRD433 RFC is fine, and as for the parameter SAPDBHOST - it is "srd433" (the correct one).

Best Regards,

Aleks

[Former Member]

Did you try to delete the jobs in DB13, and re-schedule from scratch?

[Former Member]

Hi

take a look at SAP Note : 980266 to help analysis

Mark

[Former Member]

Hi all,

@Joe Bo: yes of course - it was the first thing i did.

- Have checked the profiles

- Have restarted the system.

- have rescheduled the jobs in DB13

@Mark, like i see it, the problem is not in the connection. There are generated two of them - one false and one right. The problem is, that when the job is started, it tried to use the false one(the old database server) instead of the right one.

When the jobs started, obviously the first thing is checked is "is there a sapxpg_dbdest... connection". And when not - automaticaly to be generated one. In that sort of thinking - like i see it - the question is : when the connection is generated, from where is the data taken ?From where is taken the database server name?

Edited by: Aleksandar Georgiev on Nov 26, 2009 9:11 AM

[Former Member]

The problem is, that when the job is started, it tried to use the false one(the old database server) instead of the right one. 
When the jobs started, obviously the first thing is checked is "is there a sapxpg_dbdest... connection". And when not - automaticaly to be generated one.

I think you are right here.

For further clarification:

What is your operating system?

Then you are talking about

application server (was srv056) and database(srd455)

But on which server was the central instance ? Or is that what you called application server ?

And how did you move the servers? There are guides about homogeneous or heterogeneous system copy. Did you follow any one of them? Or did you just copy over files?

regards

[Former Member]

Our Configuration:

The OS is RedHat Linux, 2.6x.

Database Oracle 10.2.0.4

___

central instance==application server (before srv056, now srd433).

database (before srd455, now srd433).

___

We have moved the system with the help of an sap advisor.

[Former Member]

Hi,

just read back the error message and picked up on the :

COMMANDNAME = BRCONNECT
OPERATINGSYSTEM = ANYOS
TARGETSYSTEM = srd455
DESTINATION =

Now if you go to transaction SM69 "External Operating Commands" Is the command BRCONNECT have the old server assigned to it.

Regards

Mark

[Former Member]

Hi,

also have a look at table SDBAP...

[Former Member]

Yes, I think Mark spotted it.

For your old configuration you had to use some special features to be able to backup on the remote machine.

Now you shouldn't need the help of sapxpg or transaction SM69.

Have a look at your init<SID>.sap file. Perhaps best would be to configure backup from scratch, following the installation guide.

One more thing to check: Does it work from command line ?

Log in as user ora<sid> and type:

brconnect -u / -c -f check

regards