java.sql.SQLException: Invalid number format for port number

Jim pinged me with this error today:

on ./adgendbc.sh i get

Creating the DBC file...

java.sql.SQLRecoverableException: No more data to read from socket raised validating GUEST_USER_PWD

java.sql.SQLRecoverableException: No more data to read from socket

Updating Server Security Authentication

java.sql.SQLException: Invalid number format for port number

Database connection to jdbc:oracle:thin:@host_name:port_number:database failed

to this point, this is what i've tried.

clean, autoconfid on db tier, autoconfig on cm same results

bounced db and listener.. same thing.. nothing i've done has made a difference

I noticed that when this error was coming the DB alert log was showing:

Wed May 13 18:50:51 2015

Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0x8] [PC:0x10A2FFB

C8, joet_create_root_thread_group()+136] [flags: 0x0, count: 1]

Errors in file /r12.1/admin/diag/rdbms/erp/erp/trace/erp_ora_14528.trc  (incident=1002115):

ORA-07445: exception encountered: core dump [joet_create_root_thread_group()+136

] [SIGSEGV] [ADDR:0x8] [PC:0x10A2FFBC8] [Address not mapped to object] []

Incident details in: /r12.1/admin/diag/rdbms/erp/erp/incident/incdir_1002115/erp_ora_14528_i1002115.trc

Metalink search revealed this article:

Java Stored Procedure Fails With ORA-03113 And ORA-07445[JOET_CREATE_ROOT_THREAD_GROUP()+145] (Doc ID 1995261.1)

It seems that the post patch steps for a PSU OJVM patch were not done.  We followed the steps given in above note were note completed. We completed these and adgendbc.sh completed successfully after that.

1.set the following init parameters so that JIT and job process do not start.

If spfile is used:

SQL> alter system set java_jit_enabled = FALSE;
SQL> alter system set "_system_trig_enabled"=FALSE;
SQL> alter system set JOB_QUEUE_PROCESSES=0;

2. Startup instance in restricted mode and run postinstallation step.

SQL> startup restrict

3.Run the postinstallation steps of OJVM PSU(Step 3.3.2 from readme)

Postinstallation

The following steps load modified SQL files into the database. For an Oracle RAC environment, perform these steps on only one node.

1. Install the SQL portion of the patch by running the following command. For an Oracle RAC environment, reload the packages on one of the nodes.

2. cd $ORACLE_HOME/sqlpatch/19282015

3. sqlplus /nolog

4. SQL> CONNECT / AS SYSDBA

5. SQL> @postinstall.sql

6. After installing the SQL portion of the patch, some packages could become INVALID. This will get recompiled upon access or you can run utlrp.sql to get them back into a VALID state.

7. cd $ORACLE_HOME/rdbms/admin

8. sqlplus /nolog

9. SQL> CONNECT / AS SYSDBA

SQL> @utlrp.sql

4. Reset modified init parameters

SQL> alter system set java_jit_enabled = true;
SQL> alter system set "_system_trig_enabled"=TRUE;
SQL> alter system set JOB_QUEUE_PROCESSES=10;
        -- or original JOB_QUEUE_PROCESSES value

5.Restart instance as normal

6.Now execute the Java stored procedure.

Ran adgendbc.sh and it worked fine.