This blog will go straight to the topic. When upgrading\/installing your content server to 7+, you may experience an internal error with a popup telling you to look into a file called something like: DBTestResult7092863812136784595.tmp<\/p>\n
In fact, the installation process failed to test the database connection. Even if it managed to find your schema previously. In the file you’ll find something like:<\/p>\n
Last SQL statement executed by DB was:\n\n#0 0x00000033b440f33e in waitpid () from \/lib64\/libpthread.so.0\n#1 0x00000000004835db in dmExceptionManager::WalkStack(dmException*, int, siginfo*, void*) ()\n#2 0x0000000000483998 in dmExceptionHandlerProc ()\n#3 <signal handler called>\n#4 0x00007f3d8c0e7d85 in ber_flush2 () from \/dctm\/product\/7.3\/bin\/liblber-2.4.so.2\n#5 0x00007f3d8bebb00b in ldap_int_flush_request () from \/dctm\/product\/7.3\/bin\/libldap-2.4.so.2\n#6 0x00007f3d8bebb808 in ldap_send_server_request () from \/dctm\/product\/7.3\/bin\/libldap-2.4.so.2\n#7 0x00007f3d8bebbb30 in ldap_send_initial_request () from \/dctm\/product\/7.3\/bin\/libldap-2.4.so.2\n#8 0x00007f3d8beab828 in ldap_search () from \/dctm\/product\/7.3\/bin\/libldap-2.4.so.2\n#9 0x00007f3d8beab952 in ldap_search_st () from \/dctm\/product\/7.3\/bin\/libldap-2.4.so.2\n#10 0x00007f3d898f93b2 in nnflqbf () from \/opt\/oracle\/product\/client_12.1.0.2\/\/lib\/libclntsh.so\n#11 0x00007f3d898ef124 in nnflrne1 () from \/opt\/oracle\/product\/client_12.1.0.2\/\/lib\/libclntsh.so\n#12 0x00007f3d898fe5b6 in nnfln2a () from \/opt\/oracle\/product\/client_12.1.0.2\/\/lib\/libclntsh.so\n#13 0x00007f3d886cffc0 in nnfgrne () from \/opt\/oracle\/product\/client_12.1.0.2\/\/lib\/libclntsh.so\n#14 0x00007f3d887f4274 in nlolgobj () from \/opt\/oracle\/product\/client_12.1.0.2\/\/lib\/libclntsh.so\n#15 0x00007f3d886ce43f in nnfun2a () from \/opt\/oracle\/product\/client_12.1.0.2\/\/lib\/libclntsh.so\n#16 0x00007f3d886ce213 in nnfsn2a () from \/opt\/oracle\/product\/client_12.1.0.2\/\/lib\/libclntsh.so\n#17 0x00007f3d8875f7f1 in niqname () from \/opt\/oracle\/product\/client_12.1.0.2\/\/lib\/libclntsh.so\n#18 0x00007f3d88612d06 in kpplcSetServerType () from \/opt\/oracle\/product\/client_12.1.0.2\/\/lib\/libclntsh.so\n#19 0x00007f3d8861387b in kpuatch () from \/opt\/oracle\/product\/client_12.1.0.2\/\/lib\/libclntsh.so\n#20 0x00007f3d893e9dc1 in kpulon2 () from \/opt\/oracle\/product\/client_12.1.0.2\/\/lib\/libclntsh.so\n#21 0x00007f3d892e15f2 in OCILogon2 () from \/opt\/oracle\/product\/client_12.1.0.2\/\/lib\/libclntsh.so\n#22 0x0000000000555232 in DBConnection::Connect(DBString const*, DBString const*, DBString const*) ()\n#23 0x00000000005555e4 in DBConnection::DBConnection(DBString const&, DBString const&, DBString const&, DBString const&, DBStats*, dmListHead*, int, int volatile*) ()\n#24 0x000000000055f6ff in DBDataBaseImp::DBDataBaseImp(DBString const&, DBString const&, DBString const&, DBString const&, DBStats*, DBDataBase*, dmListHead*, int, int volatile*) ()\n#25 0x0000000000545aaf in DBDataBase::DBDataBase(DBStats*, DBString const&, DBString const&, DBString const&, DBString const&, dmListHead*, int, int volatile*) ()\n#26 0x0000000000466bd8 in dmServer_Dbtest(int, char**) ()\n#27 0x00000033b3c1ed1d in __libc_start_main () from \/lib64\/libc.so.6\n#28 0x0000000000455209 in _start ()\nTue Jan 8 16:18:15 2019 Documentum Internal Error: Assertion failure at line: 1459 in file: dmexcept.cxx<\/pre>\nNot so precise right?<\/p>\n
In fact, it’s pretty simple. The installer failed to use your tnsnames.ora file because LDAP auth is set with a higher priority. For those who don’t know, the tnsnames.ora holds your database connection information. You won’t be able to connect documentum without it, as documentum will try to locate it.<\/p>\n
Sometimes, depending on how the DBA installed the oracle client on the machine, LDAP identification may be set prior to the tnsnames identification. So you have two possibilities:<\/p>\n
For info, these files are located in $ORACLE_HOME\/network\/admin, by default they are installed under the Oracle user install owner. So to edit the files you must be root or ask the DBAs to do it for you.<\/p>\n","protected":false},"excerpt":{"rendered":"
This blog will go straight to the topic. When upgrading\/installing your content server to 7+, you may experience an internal error with a popup telling you to look into a file called something like: DBTestResult7092863812136784595.tmp In fact, the installation process failed to test the database connection. Even if it managed to find your schema previously. […]<\/p>\n","protected":false},"author":40,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[197,229],"tags":[1544,129,1545,1546,1547,96,1548],"type_dbi":[],"class_list":["post-12190","post","type-post","status-publish","format-standard","hentry","category-application-integration-middleware","category-database-administration-monitoring","tag-1544","tag-documentum","tag-error","tag-internal","tag-ldap","tag-oracle","tag-tnsnames"],"acf":[],"yoast_head":"\n