No space left of device, if caused on client side, usually means that somewhere you have file system full and process tried to use that file system. That would easy to check with df command for start. If you suspect something is wrong with backup configuration, you will need to share details of configuration first.
SabarnaDeb
2 Intern
•
139 Posts
1
July 3rd, 2012 12:00
Thanks Hrvoje. I was expecting response from you. I was reading one article some how related to this error.
1. I copied the RMAN backup script in /nsr/res path of oracle client. Configure in Client's Saveset attribute as "RMAN:/nsr/res/scriptname".
2. Copied "nsrnmobkp" from /usr/sbin to another name:"nsrnmodbname" and then edited below parameter.
ORACLE_HOME=
ORACLE_SID=
PATH=
ORACLE_SID=
mentioned same "nsrnmodbname" in backup command attribute of client.
We are having total 3 oracle database, for one client it is working fine but for other two oracle client it is showing same error .......
ble1
4 Operator
•
14.3K Posts
0
July 3rd, 2012 12:00
No space left of device, if caused on client side, usually means that somewhere you have file system full and process tried to use that file system. That would easy to check with df command for start. If you suspect something is wrong with backup configuration, you will need to share details of configuration first.
ble1
4 Operator
•
14.3K Posts
0
July 3rd, 2012 15:00
a) make sure that oracle client has permissions to access that script
b) usually ORACLE_HOME is enough if connect string is present (eg. not using OS auth which appears to be your case)
c) your error does not need to be related to disk space - it might be very well "memory space" - see link
I would suggest to check link under c) and check it with both OS and Oracle guys.
SabarnaDeb
2 Intern
•
139 Posts
0
July 3rd, 2012 19:00
Sure I will check...Thanks....