Forum Discussion
Thank you.
1. Yes, all that works
2. That wasn't very informative as well. Sample what I get:
16:22:10.372 [18972] <16> child_fork: from BPRD_GET_BPLIST, bp error = no entity was found
16:22:36.193 [18987] <16> child_fork: from BPRD_GET_BPLIST, bp error = no entity was found
16:23:19.914 [19074] <16> child_fork: from BPRD_GET_BPLIST, bp error = no entity was found
16:24:20.052 [19171] <16> child_fork: from BPRD_GET_BPLIST, bp error = no entity was found
16:24:55.262 [19193] <16> child_fork: from BPRD_GET_BPLIST, bp error = no entity was found
But good news I was able to get closer to finding root cause. It is something related to user permissions.
Because if on problem client I will check from root - I am able to see oracle backup files.
So I asked for sudo permission for oratest user and checked same command but with sudo:
sudo bin/bplist -C r12db -S backup-a -k r12db_db -t 4 -R /
which happily listed oracle backup files.
Testdb3 server (problem one)
bash-4.2$ id oratest
uid=1001(oratest) gid=1001(oratest) groups=1001(oratest),10(wheel),201(dba)
doesn't show without sudo
testdb2 server
[oratest@testdb2 ~]$ id oratest
uid=510(oratest) gid=200(dba) groups=200(dba)
Works OK as is. Only differece I see is gid, but Unix team says it shouldn't matter, and will look at it later.
So I figured it out. Problem was to assign same gid to user (dba (gid=200) in my case on prod) as where backup was made.
sudo usermod -g 201 oratest (201 = dba on destination server)
and everything works.
Related Content
- 3 months ago
- 10 years ago
- 5 months ago
- 21 days ago