After having a problem with my external drive, I had to re-import the old images in a new VirtualBox installation and started facing the following error:
Document is empty.
Location: 'D:\VirtualBox VMs\Ubuntu 18.04\Ubuntu 18.04.vbox', line 1 (0), column 1.
Ok, so after navigating to that directory and opening the referred vbox file (Ubuntu 18.04.vbox), I realized it was empty.
Fear not! In the same folder should exist another file with .vbox-prev extension. All you need to do is to delete this 0-byte file, rename the .vbox-prev to .vbox and re-import it.
Best of luck!
Tuesday, April 30, 2019
Saturday, April 27, 2019
Siebel Install Database Error: set_unicode.sql not found
When doing a fresh install of Siebel version IP19.2 on an Oracle Linux 7.6 server, I faced the following error during the database installation:
UpgradeLog UpgradeInfo 3 0000000254e42d16:0 2019-04-18 19:28:43 Status Message (Executing SQL statements in file /opt/siebel/ses/dbsrvr/oracle/set_unicode.sql ...)
Trace Trace 3 0000000254e42d16:0 2019-04-18 19:28:43 Unable to open file 'set_unicode.sql'.
After a long night of research I figured out that this error was caused by a error that happened during the Siebel binaries installation, as seen in the $SIEBEL_ROOT/cfgtoollogs/oui path:
$ ls -ltr *.err
I found non-zero .err files, so taking a closer look to these files, this is what I found:
java.io.IOException: Cannot run program "/bin/csh": error=2, No such file or directory at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048)
With the above error message I was able to identify that the root cause of the error was the lack of c shell installation on my server, so I simply ran:
yum install tcsh
It is important to note that, after installing the c shell lib, I re-installed Siebel from scratch and everything ran smoothly =)
UpgradeLog UpgradeInfo 3 0000000254e42d16:0 2019-04-18 19:28:43 Status Message (Executing SQL statements in file /opt/siebel/ses/dbsrvr/oracle/set_unicode.sql ...)
Trace Trace 3 0000000254e42d16:0 2019-04-18 19:28:43 Unable to open file 'set_unicode.sql'.
After a long night of research I figured out that this error was caused by a error that happened during the Siebel binaries installation, as seen in the $SIEBEL_ROOT/cfgtoollogs/oui path:
$ ls -ltr *.err
I found non-zero .err files, so taking a closer look to these files, this is what I found:
java.io.IOException: Cannot run program "/bin/csh": error=2, No such file or directory at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048)
With the above error message I was able to identify that the root cause of the error was the lack of c shell installation on my server, so I simply ran:
yum install tcsh
It is important to note that, after installing the c shell lib, I re-installed Siebel from scratch and everything ran smoothly =)
Friday, April 26, 2019
ODBC error 81 in SQLConnect
After installing Oracle Client 12.2.0.1 (32-bit) and Siebel IP17, one of the mandatory steps is to test connectivity to the Database using odbcsql command, like:
odbcsql /u <db_username> /p <db_password> /s <DSN_Name>
But I wasn't able to get it to work, instead I was facing the below error:
Logging into "SiebelInstall_DSN" as "SIEBEL" ...
ODBC error 81 in SQLConnect:
523 80
(native error 0).
Unable to login using specified ODBC parameters.
odbcsql /u <db_username> /p <db_password> /s <DSN_Name>
But I wasn't able to get it to work, instead I was facing the below error:
Logging into "SiebelInstall_DSN" as "SIEBEL" ...
ODBC error 81 in SQLConnect:
523 80
(native error 0).
Unable to login using specified ODBC parameters.
After some troubleshooting I was able to solve it after creating a symbolic reference for libclnst lib:
cd $ORACLE_HOME/lib
ln -s libclntsh.so.12.1 libclntsh.so
Subscribe to:
Posts (Atom)