Skip to Content

Hi Folks,

Recently we have some customers are meeting such kind of error when connecting REMOTE oracle database:

C  *** ERROR => SAP kernel 7XX with basic release 7XX only supported with Oracle server >= 11.2

Because of this error, the database connection was not closed, then the further db connection failed again, again, leaving many unclosed connection, thus overflow error may occur:

Max. number of open Oracle db connections (16) exceeded.

This error occurs after kernel upgrade. This error is supposed to only occur for SAP on oracle, but not for oracle as a remote database. There is little limitation on remote oracle, so most of oracle versions are still supported by sap kernels as long as the oracle is a secondary database/remote database. New oracle dbsl will be released to fix this issue.


So whenever you are meeting this error for remote oracle, please check if the dbsl is the latest. In case the latest oracle dbsl is not solved, please contact SAP support. Please do not simply upgrade the remote database as the error “implicts”.

Best regards,
James

To report this post you need to login first.

12 Comments

You must be Logged on to comment or reply to a post.

  1. Former Member

    Zhang,

    Did you find the solution for this issue ?

    Here I`m using the KERNEL 7.45 with lastest patch including dbsl, and have the same issue connecting to remote Oracle Database.

    The message on the WP are

    C  e: OCIStmtExecute() failed with -1=OCI_ERROR, SQL error 942: C  Couldn’t read V$INSTANCE (con=9): sqlcode=942 C  e: OCIStmtExecute() failed with -1=OCI_ERROR, SQL error 942: C  Couldn’t get creation timestamp from V$DATABASE: sqlcode=942 C  *** ERROR => SAP kernel 745 with basic release 740 only supported with Oracle server >= 11.2 [dbsloci.c    2893]

    (0) 
    1. James Zhang Post author

      Actually we have a note 2304361 for this issue. Are you sure you are using latest dbsl?
      Can you share the complete dev trace?

      (0) 
          1. James Zhang Post author

            The error means the remote oracle user does not have enough permission, say the user you used to connect oracle does not have access to v$database. You can simply verify this via sqlplus to log on the user you used from hana:

            select * from v$database;

            I believe the same error will occur.

             

            (0) 
            1. Mohamed Al Homsi

              Dear James ,

              Please i need to inform you sometimes(little) the connection give me successfully connected , and also it connected successfully from hana studio using (SDA) .

              and see the error :

               

              Best Regards,

              Homsi

              (0) 
              1. James Zhang Post author

                Hi Homsi,

                Connection works fine, however the user does not have permission to query v$database, thus you saw the error from SAP work process trace.

                Best regards,
                James

                (0) 
    1. James Zhang Post author

      yeah, you see, it means the user doesn’t have permission to v$database. To prove this , you can grant select_catalog role to the user.

      (0) 

Leave a Reply