on 2009 Jan 26 5:23 AM
Hi all,
In my landscape we scheduled the backup ECC - oracle in our data centre. The back up and redo logs are running successfully. Now we are moving the data centre to someother location, so I tried to change the parameter in init<sid>.sap.
I changed the following parameters.
backup_root_dir =
192.12.7.224\backup\newserver
stage_root_dir =
192.12.7.224\backup\newserver
archive_copy_dir =
192.12.7.224\backup\newserver
archive_stage_dir =
192.12.7.224\backup\newserver
But the result is its not able to find the directory in the logs.
Actions taken :
I tried to access the data center from the server and its able to login with SIDADM without prompting for userid password.
But still its showing the same error , by displaying the error message as " the directory is not able to found ".
Regadrs
Vijay
Hi VIjay,
> I tried to access the data center from the server and its able to login with SIDADM without prompting for userid password.
>
> But still its showing the same error , by displaying the error message as " the directory is not able to found ".
is the system running on Windows? If so, make sure that the access to the remote folders also works for SAPSERVICE<SID>, as this is the usercontext the work processes and the brtools called by the work processes run in.
regards,
Lars
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi all,
In my landscape we scheduled the backup ECC - oracle in our data centre. The back up and redo logs are running successfully. Now we are moving the data centre to someother location, so I tried to change the parameter in init<sid>.sap.
I changed the following parameters.
backup_root_dir =
192.12.7.224\backup\newserver
stage_root_dir =
192.12.7.224\backup\newserver
archive_copy_dir =
192.12.7.224\backup\newserver
archive_stage_dir =
192.12.7.224\backup\newserver
The log files are shows
Job started
Step 001 started (program RSDBAJOB, variant &0000000000717, user ID ADMIN)
Execute logical command BRARCHIVE On host Newr3GLD
Parameters: -u / -c force -p initGLD.sap -s
BR0002I BRARCHIVE 6.40 (45)
BR0282E Directory '
212.49.9.112\backup\frer3GLD' not found
BR0182E Checking parameter/option 'archive_copy_dir' failed
BR0007I End of offline redo log processing: adzszwmb.log 2009-01-20 15.31.21
BR0280I BRARCHIVE time stamp: 2009-01-20 15.31.22
BR0005I BRARCHIVE terminated with errors
External program terminated with exit code 3
BRARCHIVE returned error status E
Job finished
But the result is its not able to find the directory in the logs.
Actions taken :
I tried to access the data center from the server and its able to login with SIDADM without prompting for userid password.
But still its showing the same error , by displaying the error message as " the directory is not able to found ".
Note : The same job is working in the existing data centre but not able to run in the new one.
The networks is accessible without any issues (Its not prompting for Userid and password). Even i am able to log in SIDADM.
Regadrs
Vijay Kumar
Hi,
did you read Lars reply.
It does not look like it, because your answer is exactly the same as your original post.
I'll try to repeat, with different words.
You are working on windows.
On windows there are two different users to manage SAP.
One is the <SID>adm. This user is only to perform administrative task.
The other user is SAPSERVICE<sid>. This is the real user under which SAP is running.
If you do something from "inside" SAP (like any job in DB13) it will be executed by this user (SAPSERVICE<SID>)
Therefore, trying anything from the command prompt with the user <SID>adm will make no difference as the real user running SAP is SAPSERVICE<SID>
this means that, if you want to do a test, what you have to do is the same as you have done with <SID>adm and repeat it with SAPSERVICE<SID> from the command prompt
Hi Lars and Fidel,
I am sorry, actually I didn't reply for Lars question I was trying to edit my post with full logs,before that lars raised a question so there is a mess in the post and also I am sorry for the late reply.
Answers for your question. Yes, I can access like SIDADM without any errors. Its a windows version.
But still the same error is persisting -- directory not found .I am confused totally because I just tried to take a backup in the old datacentre by changing the above mentioned parameters and it got completed successfully. But the same is not working while trying to change the parameters in new datacentre.
I don't find any problem in the new datacentre because we have changed the same in other SAP server (SQL) and its running successfully.
Kindly suggest me with your valuable points.
Thanks and regards
Vijay
Hi Vijay,
It seems
192.12.7.224\backup\newserver is a network share name. I am assuming that backup is not an network share. BRtools are not able to write on network share directly but they can write in a folder on network share. so my recommendattion is create some directory on
192.12.7.224\backup\newserver i.e..,
192.12.7.224\backup\newserver\test now you can able to take backup in folder test. Just check.
Thanks,
Kiran.
Edited by: kiran kumar vejendla on Jan 28, 2009 10:27 PM
Dear all,
I have tried all the things which you suggested me but still the same error.
Actions taken :
Created a New folder under the network shared folder eg (
192.12.7.224\backup\newserver\test)
SAPseviceSID is a service user hence I am not able to log in but I have tried the permission from Command Prompt level.
Anything I am missing still.
Regards
Vijay
Hello Nikunj,
Thanks for your reply.
I mapped the drive as like you have mentioned and then I have changed the parameters as well.
These drives were mapped
192.12.7.224\backup as X:
backup_root_dir = X:\newserver\test
stage_root_dir = X:\newserver\test
archive_copy_dir = X:\newserver\test
archive_stage_dir = X:\newserver\test
The same error is still persisting.
Regadrs
Vijay Kumar
Dear Vijay,
Thanks.
Please try with
These drives were mapped
192.12.7.224\backup as X:
backup_root_dir = X:\newserver\test\
stage_root_dir = X:\newserver\test\
archive_copy_dir = X:\newserver\test\
archive_stage_dir = X:\newserver\test\
I assume when you access X: drive you get newserver as directory and test as subdirectory of newserver.
Regards,
Nikunj Thaker.
Edited by: Nikunj Thaker on Jan 29, 2009 12:30 PM
Yes. Because "X:" is not know to SAPService<SID> user - which is actually executing the backup if you start it from DB13.
You can use UNC names
<ip>\share
but
You must create the user SAPService<SID> (not SIDADM) on the target server with the same password you gave it during the installation.
I would then create an external command in transaction SM49 such as "dir
<ip>\share" and execute it to see if that UNC path is reachable.
Again: All things you do under logged on user SIDADM are useless.
Markus
Hi Vijay,
Your log is showing that it is unable to find
212.49.9.112\backup\frer3GLD'
BR0282E Directory '
212.49.9.112\backup\frer3GLD' not found
BR0182E Checking parameter/option 'archive_copy_dir' failed
Everytime you are telling same error message but never gave latest log to support you. I am not sure whether you are correctly updating your config file. If you are not providing enough information, forum cannot support you tooo...
Correct above error and try....
Thanks,
Kiran.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Kiran,
Thanks for your suggestion.
But I like to suggest you that please read the post from the beginning. Since it is the same error and the same log I dont want to keep on posting the same logs.Obvisouly if the log is different for sure I would have posted.
Thanks for everyone that I solved my problem the reason for the same its due to some inconsistency in the hardware level and also the main reason for the issue is the SAPServiceSID is locked due to wrong attempts.
Thanks for all your suggestions and the point swill be rewarded for the same.
Regards
Vijay
User | Count |
---|---|
66 | |
10 | |
10 | |
10 | |
10 | |
8 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.