cancel
Showing results for 
Search instead for 
Did you mean: 

Brtools problem after Oracle 122. Upgrade - libmql1.so: cannot open shared object file

DieterLorenz
Active Participant
0 Kudos

Hello,

getting this error after starting a archive log backup. The permission br* files in kernel exe are oracle:oinstall,

-rwsrwsr-- 1 oracle oinstall 10872630 2018-11-28 11:18 brarchive
-rwsrwsr-- 1 oracle oinstall 10977861 2018-11-28 11:18 brbackup
-rwsrwsr-- 1 oracle oinstall 13174767 2018-11-28 11:18 brconnect
-rwsrwsr-- 1 oracle oinstall 11460555 2018-11-28 11:17 brrecover
-rwsrwsr-- 1 oracle oinstall 6532552 2018-11-28 11:18 brrestore
-rwsrwsr-- 1 oracle oinstall 13763363 2018-11-28 11:18 brspace
-rwxr-xr-x 1 sp1adm sapsys 7151798 2018-11-28 11:18 brtools

permissions and links from /oracle/client are the same like sidadm:sapsys

-r--r--r-- 1 sp1adm sapsys 319 2018-11-28 12:51 dbclient.lst
lrwxrwxrwx 1 sp1adm sapsys 19 2018-11-28 12:53 instantclient -> instantclient_12201
drwxr-xr-x 2 sp1adm sapsys 4096 2018-11-28 12:51 instantclient_12201

Error Message in brtools and db13

brarchive -p initSP1.sap -save -d disk -k no -l E -u //
and testet with -u /
brarchive: error while loading shared libraries: libmql1.so: cannot open shared object file: No such file or directory

Any ideas ? Thanks a lot

Accepted Solutions (0)

Answers (3)

Answers (3)

DieterLorenz
Active Participant

You are right - oracle client use the 122 folder

ln -s /oracle/client/12x_64 122
ln -s /oracle/client/12x_64 12x

Reagan
Advisor
Advisor
0 Kudos

After creating the symbolic links did it fix the problem?

DieterLorenz
Active Participant
0 Kudos

yes sure, you can have a look at the .dbenv.sh files there is the client location ...

Reagan
Advisor
Advisor
0 Kudos

Have you tried the recommendation given here?

https://answers.sap.com/questions/205064/libmql1so-cannot-open-shared-object-file.html

What happens when you run the brarchive command from the OS level?