Database connection on Enterprise Server

I have a trouble on my Enterprise server after Installing "Installation plan". When starting service there are some problems with database connecting.
___________________________________________________________
Information in jde.log:
4048/2940 MAIN_THREAD Mon Feb 11 18:30:44.715002 ipcmisc.c299
process 4048 <jdenet_k> registered in entry 1

4048/2940 MAIN_THREAD Mon Feb 11 18:30:44.731001 Netcfg.c266
Starting Kernel of Type:METADATA KERNEL

4048/2940 MAIN_THREAD Mon Feb 11 18:30:45.746002 ServerDispatch.cpp66
INITIALIZING METADATA SERVER KERNEL

4048/2940 MAIN_THREAD Mon Feb 11 18:30:52.496001 dbinitcn.c884
OCI0000065 - Unable to create user session to database server

4048/2940 MAIN_THREAD Mon Feb 11 18:30:52.496003 dbinitcn.c889
OCI0000141 - Error - ORA-01017: invalid username/password; logon denied

4048/2940 MAIN_THREAD Mon Feb 11 18:30:52.496006 Jdb_drvm.c776
JDB9900164 - Failed to connect to ORADB

4048/2940 MAIN_THREAD Mon Feb 11 18:30:52.496008 Jtp_cm.c273
JDB9909003 - Could not init connect.

4048/2940 MAIN_THREAD Mon Feb 11 18:30:52.496010 Jtp_tm.c1130
JDB9909100 - Get connect info failed: Transaction ID =

4048/2940 MAIN_THREAD Mon Feb 11 18:30:52.496012 Jdb_rq1.c2226
JDB3100013 - Failed to get connectinfo

4048/2940 MAIN_THREAD Mon Feb 11 18:30:52.496015 Jdb_omp1.c3334
JDB9900257 - Failed to open F986101

jdedebug.log
Feb 11 18:30:52.168011 - 4048/2940 MAIN_THREAD Entering JDB_OpenTable(Table = F986101)
Feb 11 18:30:52.168012 - 4048/2940 MAIN_THREAD Ini file returned Language Code=||
Feb 11 18:30:52.168013 - 4048/2940 MAIN_THREAD Entering GetSystemDecimalSep.....
Feb 11 18:30:52.168014 - 4048/2940 MAIN_THREAD Profile String for DecimalSeparator=::
Feb 11 18:30:52.168015 - 4048/2940 MAIN_THREAD Try to fetch proxy info from cache
Feb 11 18:30:52.340000 - 4048/2940 MAIN_THREAD Database driver name is 'jdboci101.DLL'
Feb 11 18:30:52.356000 - 4048/2940 MAIN_THREAD Exited CreateCriticalSections_oracle with ref cnt 1
Feb 11 18:30:52.403000 - 4048/2940 MAIN_THREAD ORACLE DBInitDrv envr=053CC3B0
Feb 11 18:30:52.496000 - 4048/2940 MAIN_THREAD OCI0000065 - Unable to create user session to database server
Feb 11 18:30:52.496002 - 4048/2940 MAIN_THREAD OCI0000141 - Error - ORA-01017: invalid username/password; logon denied
Feb 11 18:30:52.496004 - 4048/2940 MAIN_THREAD ORACLE DBInitCon envr=053CC3B0 conn=053E14D8 JDECLU A (@ORADB) V0 Unicode=Y (srvrusers=1) 1
Feb 11 18:30:52.496005 - 4048/2940 MAIN_THREAD JDB9900164 - Failed to connect to ORADB
Feb 11 18:30:52.496007 - 4048/2940 MAIN_THREAD JDB9909003 - Could not init connect.
Feb 11 18:30:52.496009 - 4048/2940 MAIN_THREAD JDB9909100 - Get connect info failed: Transaction ID =
Feb 11 18:30:52.496011 - 4048/2940 MAIN_THREAD JDB3100013 - Failed to get connectinfo
Feb 11 18:30:52.496013 - 4048/2940 MAIN_THREAD Exiting JDB_OpenTable(Table = F986101) with Failure
Feb 11 18:30:52.496014 - 4048/2940 MAIN_THREAD JDB9900257 - Failed to open F986101
Feb 11 18:30:52.496016 - 4048/2940 MAIN_THREAD Couldn't find role list for user JDE.
Feb 11 18:30:52.496017 - 4048/2940 MAIN_THREAD Entering JDB_OpenTable(Table = F986101)
Feb 11 18:30:52.543000 - 4048/2940 MAIN_THREAD OCI0000065 - Unable to create user session to database server
Feb 11 18:30:52.543002 - 4048/2940 MAIN_THREAD OCI0000141 - Error - ORA-01017: invalid username/password; logon denied
Feb 11 18:30:52.543004 - 4048/2940 MAIN_THREAD ORACLE DBInitCon envr=053CC3B0 conn=054AADD0 JDECLU A (@ORADB) V0 Unicode=Y (srvrusers=1) 2
Feb 11 18:30:52.543005 - 4048/2940 MAIN_THREAD JDB9900164 - Failed to connect to ORADB
Feb 11 18:30:52.543007 - 4048/2940 MAIN_THREAD JDB9909003 - Could not init connect.
Feb 11 18:30:52.543009 - 4048/2940 MAIN_THREAD JDB9909100 - Get connect info failed: Transaction ID =
Feb 11 18:30:52.543011 - 4048/2940 MAIN_THREAD JDB3100013 - Failed to get connectinfo
Feb 11 18:30:52.543013 - 4048/2940 MAIN_THREAD Exiting JDB_OpenTable(Table = F986101) with Failure
_________________________________________________________________

At the same time there are two sessions in my database from jdenet_k.exe process (selecting something from F98OWSEC).
Also when building server packadge an error showed on my deployment server "Could not determine driver for database type O"

__________________________________
JD Edwards 8.12;Oracle Database 10.2.0.1; OS Windows 2K3 SP2

The 2 kernels that show as running processes don't mean anything at this stage. Were you able to run a successful PORTTEST? Is your security server already configured? Since the first error message has to do with an invalid username/password, have you tried to log into Oracle SQL*Plus manually with that username and password?

porttest utility show following:
Running porttest for JDE on PY812,...

Initializing Environment PY812,...
Initialization of environment failed - rcode = 0
See host services check-list for details.

Porttest failed.
See the host services check-list for details.

All Done!
Bye!


when connecting by telnet utility on port 6014 all sucessfull.

conn JDE/JDE@ORADB
was sucessfull and select from tables.

jde.ini setiings seems to be correct.
What means security server configured. Probably that was done, but I'm not shure.

Failed PORTTEST = Bad

Hopefully, you've have some files in the log directory where we can look to troubleshoot what happened. I suggest you clear the log directory, try PORTTEST again, and look through the new log files.

For the security server, you need to look at the JDE.INI on your enterprise server. Look for the section starting with [SECURITY]. You should see SecurityServer, User, and Password immediately following. Are these lines configured, meaning are they equal to some value?

PORTTEST does not work well in all cases. There are so many instances in the Customer connection why porttest fails.

You have wrong [DB_System_Settings] parameters in your enterprise server JDE.ini file. Those settings are used to connect to the Server map datasource for SVM812 owner bootstrap tables. You need to specify the correct JDE System user ID and password in that section and also the same User ID and password must match the Security section (E1 Regular User ID).

Thanks to all I have fixed problems with my Enterprise server PORTTEST utility works properly!, but still there is a problem with Packadge build procedure.

Client packadge buld completes sucessfully, but when the server backagde build start on my console the meggage appeared:
"PeopleSoft Error

Cannot determine database drive named for driver type "O"
"
After Ok button click on this message Batch application (wich builds server packedge) starts but comletes with error (nothing build).

in jde.log file

In jde.log file ther is this messages:

976/2844 WRK:Starting jdeCallObject Mon Feb 11 22:55:20.396127 pkgInit.cpp739
PKGINT0023 - Package: PY812FB. PathCode: PY812. Update checkin. Do not wait for BUSBUILD. Data by PathCode. Full/Partial Package. Include SYS, and DATA by default.

976/2844 FOREIGN_THREAD Tue Feb 12 02:21:36.297000 Jdekprnt.c1027
KNT0000119 - PRTTable_GetDefaultPrinterInfo failed to find printer: User: JDE Host: WinClient

976/2844 WRK:Starting jdeCallObject Tue Feb 12 02:22:19.952002 jdepref.c208
GetRecipientPreferences :No email address found for contact, assuming workcenter email an8<1> idln<0>

976/2844 WRK:Starting jdeCallObject Tue Feb 12 02:22:19.999042 jdepref.c208
GetRecipientPreferences :No email address found for contact, assuming workcenter email an8<1> idln<0>

2244/2360 MAIN_THREAD Tue Feb 12 02:22:22.515001 Jdb_drvm.c460
JDB9900436 - Cannot determine database driver name for driver type "O"

Please help what can it be.

The --Cannot determine database drive named for driver type "O"-- error typically points to an issue with your Oracle Client install. The fact that your client build succeeds tells me that your Oracle Client is at least working in some fashion. I see this error most often when the Oracle Client software version is older than the Oracle server version. Are you sure that your Oracle client and server are at the same release and patch levels?

I have also seen this error intermittently with a 10GR1 site of mine that has all the Oracle clients and the Oracle server at the same release and patch levels. This error is seen sporadically when working with applications that use tables that contain BLOBs such as Central Objects tables. It shows up most in OMW and UTB. This has also happened occasionally with the package build process. We have reported the issue to Oracle but as it is not reproducible and does not produce any SQLNET logs when it happens we have not gotten anywhere with Oracle support.

If you restart the package build from the package build history does your server build fail consistently?

The server package will also fail if you don't turn on your security server in the client JDE.INI on the machine you're building the package on. Turn it on if it's not on already and then log in again and give it a try.

Thank you for your reply.
The version of Oracle client software that is used on my Deplyment server is 10.2.0.1 (the same as on Oracle Database Server). Also I've tried to use UTB with tables where BLOB fields present and UTB works propely (as I think) no error messages appeared, all data was selected.
I have reinstalled Oracle client on Deplyment server and tried rebuild of packadge, but this error still exists when starting server packadge build.