Db2

Db2

Where DBAs and data experts come together to stop operating and start innovating. Connect, share, and shape the AI era with us.


#Data


#Data
#Databases
#Operatingsystems
#Db2
#Databasesolutions
 View Only

  • 1.  Baffling SQL30090N Error

    Posted 03/14/24 05:10 PM

    Team,

    I am working on a brand new Db2 v11.5.8 database in Azure (which I didn't create or provision).

     

    Logged onto the database server I issue

    db2 "create table try ( col1 char(5) not null ) in userspace1"

    and it works fine.

     

    If I attempt he same command on a client connected to the database server I receive a SQL30090N Reason code 1.

    https://www.ibm.com/support/pages/sql30090n-reason-code-1-or-7-returned-application-against-db2-database-server

     

    The IBM Support link says to issue

    db2set DB2COMM=TCPIP

    db2 update dbm cfg using SVCENAME 12345

    and stop/start the instance.

     

    Here is what happens from a remote client:

    C:\IIDR>db2 connect to DB1 user user

    Enter current password for user:

     

       Database Connection Information

     

    Database server        = DB2/LINUXX8664 11.5.8.0

    SQL authorization ID   = USER

    Local database alias   = DB1

     

     

    C:\IIDR>db2 "select * from sysibm.sysdummy1"

     

    IBMREQD

    -------

    Y

     

      1 record(s) selected.

    So I know the database client connection is correct. But

     

    C:\IIDR>db2 "create table try ( col1 char(5) not null ) in userspace1"

    DB21034E  The command was processed as an SQL statement because it was not a

    valid Command Line Processor command.  During SQL processing it returned:

    SQL30090N  Operation invalid for application execution environment.  Reason

    code = "1".  SQLSTATE=25000

     

    +-------------------------------------+---------------------------------------------+

    | Frank C. Fillmore, Jr.              | Office: 410.465.6335  Mobile: 410.963.0416  |

    | The Fillmore Group, Inc. (TFG)      | Facsimile: 888.828.4717                     |

    | 11 West Mount Vernon Place; Room 2  |                                             |

    | Baltimore, Maryland 21201           | URL: https://www.thefillmoregroup.com       |

    | USA                                 | Blog: https://www.thefillmoregroup.com/blog |

    +-------------------------------------+---------------------------------------------+

    ImageImage

     



  • 2.  RE: Baffling SQL30090N Error

    Posted 03/15/24 01:45 AM

    Hi Frank,

    interesting problem! My first guess was, that try could be a reserved word.

    But looking closely at SQL30090N points to configuration settings of the instance. Can you do other write operations in the database? Like updating a value in e.g. SYSSTAT tables for statistics, or check the variables for 2PC like TM_DATABASE, TP_MON_NAME. And maybe check the Db connect type https://www.ibm.com/docs/en/db2/11.5?topic=commit-connecttype

    maybe the error message isn't that misleading, if these parameters are not correct. Mostly the default value will be the good and less problematic ones.

    Cheers
    Roland



    ------------------------------
    Roland Schock
    IBM Champion and IBM Gold Consultant
    ------------------------------



  • 3.  RE: Baffling SQL30090N Error

    Posted 03/25/24 06:43 AM

    Hello there

    Seeing your error and the support page my first question would be if you also see the SYNCLOG and the "read only" error in your diaglog?

    The servicename/port solution seems to be for the RC7.

    Nonetheless both RCs seem to come from DRDA. Have you tried the same via an ODBC or JDBC connection?

    Regards

     Sebastian



    ------------------------------
    Sebastian Zok
    Senior Database Administrator
    Cancom Managed Services GmbH
    ------------------------------



Related Content