Tag Archives: SQL

Perfectly solve the 1366 error of saving Chinese in MySQL

Most recently when using SQLAlchemy to store Chinese in a table in a mysql database:
Warning Code: 1366 penstring value: ‘\xE5\x9C\xA8’ for column ‘content’ at row 1
This is because we store Chinese, and our table does not support Chinese character set. We use show variables like ‘character%’. View mysql’s current encoding:

It can be seen that the character set of database and Server USES latin1, and latin1 does not support Chinese, which leads to the error of storing Chinese.
I tried two ways to avoid the Chinese storage error problem:
1: Set server and Database to UTF8 type
Use the following command to set input on the command line:
Show variables like ‘% char %’;
set character_set_server = utf8;
set character_set_database = utf8;
Use the command above. If not, show Create table. To see if the specific column has the wrong character set.
2: Set the default character set when building the table
When I build tables, I usually set the default character set to UTF8 in the SQL statement to avoid some problems:

sql='''create table analysis(city varchar(20),companySize varchar(20),education varchar(20))default charset=utf8'''

The default Charset = UTf8 is added at the end of the statement to set the default charset= UTf8, or at the end of the SQL statement if additional parameters need to be set.
 
★★★★★ ★★ warm tips:
This is a people encounter a problem, here said once: when using SQL statements, some of the words, letters is a class of special characters similar to python, import, etc., so if you want to use the key words, need to add the quotes ` to it, such as ` index `, the index is the key word, if used directly, will be an error. Therefore, I need to pay special attention to the fact that I always make mistakes when using it. I just can’t find the problem and think of other mistakes. Fortunately, I suddenly remember this problem mentioned by the database teacher accidentally.
 

You can’t specify target table ‘car’ for update in from clause

Error Code: 1093 occurs when the following SQL statement is executed:

update car set tag = 1 where id in (select id from car where brand_id=182 and tag=0);

The reason for the error is that the modified table and the queried table are the same table, which is not allowed in MySQL. We can solve this problem by querying again in the middle:

update car set tag = 1 where id in (select id from (select id from car where brand_id=182 and tag=0) As temp);

MySQL workbench insert data prompt error: 1046 (errorcode: 1046. No database select…)

Problem description:
The Error Code: 1046. Select the default DB to be 2 by double – clicking its name in the SCHEMAS list in the sidebar. 0.000 SEC

Error: The default database was not selected to receive the data
Solution: 1. Double-click the database you want to operate on
2. Execute the SQL statement
3. Check whether the data was inserted successfully

SQL Error: 904, SQLState: 42000

Question:

WARN 2011-03-04 09:33:18 org.hibernate.util.JDBCExceptionReporter – SQL Error: 904, SQLState: 42000

the ERROR 2011-03-04 09:33:18 org. Hibernate. Util. JDBCExceptionReporter – ORA – 00904: “MENU0_”. “MENU_OPEN_IN_HOME” : identifier is invalid

Hibernate: select portletloc0_.PORTLET_LOCATION_ROW as col_0_0_, portletloc0_.PORTLET_LOCATION_COLUMN as col_1_0_, portlet1_.PORTLET_URL as col_2_0_, portlet1_.PORTLET_TITLE as col_3_0_, portletloc0_.PORTLET_ID as col_4_0_ from JEDA_PORTLET_LOCATION portletloc0_, JEDA_PORTLET portlet1_ where portletloc0_.PORTLET_ID=portlet1_.PORTLET_ID and portletloc0_.POSITION_ID=?order by portletloc0_.PORTLET_LOCATION_ROW asc, portletloc0_.PORTLET_LOCATION_COLUMN asc

2011-3-4 9:33:18 org.apache.catalina.core.StandardWrapperValve invoke

severity: servlet.service () for Servlet DispatcherServlet threw exception

java.sqlexception: “MENU0_”.”MENU_OPEN_IN_HOME”: identifier is invalid

the reason:
The attribute name of the
hbm. XML file does not correspond to the attribute name of the database

DB2 SQL error: sqlcode = – 803, sqlstate = 23505, sqlerrmc = 2 [solution]

DB2 SQL Error: SQLCODE=-803, SQLSTATE=23505, SQLERRMC=2.
1, check under, probably means to violate the uniqueness constraints ah!
2. However, I found in DB2 DESCRIBE table XX that only ID of the table cannot be empty.
3, finally, directly wrote a SQL execution on the command line, the same error and code
Finally, I looked up the index in the following table and realized that a composite index had been created.
It turns out that the DBA created a unique constraint and index yesterday!
Although only ID cannot be null in a describe, the addition of a unique constraint and index results in the inability to insert data.
 

Summary of database

Group By
Group By and aggregation function can be used to achieve Group accumulation. For example, if you were asked to display the salary totals for each
department, you could use the following statement.
SELECT department_number
,SUM (salary_amount)
FROM employee
GROUP BY department_number;

result:
department_number Sum(salary_amount)
401 74150.00
403 80900.00
301 58700.00

note that all the fields accumulated without grouping in the SELECT clause must appear in the
GROUP BY clause, otherwise the following error message will be returned:
ERROR: 3504 Selected non-aggregate values must be part of the associated group.

for the above example the Department_Number field is not accumulated so it must appear in the group
BY clause. This basic rule must be borne in mind.

WHERE clause and GROUP BY clause
WHERE clause and GROUP BY clause
WHERE clause and GROUP BY clause are used together, GROUP BY only performs grouping aggregation calculation on data records that conform to the WHERE limit
system. In other words, the WHERE sub-
sentence removes unqualified data records before doing the actual aggregate calculation. What’s the combined salary for department 401 and 403?
SELECT department_number
,SUM (salary_amount)
FROM employee
WHERE department_number IN (401, 403)
GROUP BY department_number
;

results:
department_number Sum (salary_amount)
403 80900.00
401 74150.00

GROUP BY and ORDER BY
after the GROUP BY, ORDER BY makes the grouping statistics show
in the specified ORDER. For example, to show the number of people in a department, the total salary, the highest salary in a department, the lowest salary in a department
, and the average salary in a department by department number, you can use the following SQL statement:
SELECT department_number (TITLE ‘DEPT’)
,COUNT (*) (TITLE ‘#_EMPS’)
,SUM (salary_amount) (TITLE ‘TOTAL’)
(FORMAT ‘zz, ZZZ,zz9.99’)
,MAX (salary_amount) (TITLE ‘HIGHEST’)
(FORMAT ‘ ‘zz, ZZZ,zz9.99’)
,MIN (TITLE ‘amount)
(FORMAT ‘zz, ZZZ,zz9.99’)
,AVG (TITLE ‘AVERAGE’)
(FORMAT ‘zz, ZZZ,zz9.99’)
FROM employee
GROUP BY department_number
ORDER BY department_number
;

results are as follows:
DEPT #_EMPS TOTAL LOWEST AVERAGE
301 3 116,400.00 57,700.00 29,250.00 38,800.00
401 7 245,575.00 46,000.00 24,500.00 35,082.14
403 6 233,000.00 49,700.00 31,000.00 38,833.33

SELECT department_number AS DEPT
,COUNT (*) AS #_EMPS
,CAST (SUM (salary_amount) AS FORMAT ‘zz, ZZZ,zz9.99’)
AS TOTAL
,CAST (MAX (salary_amount) AS FORMAT ‘zz, ZZZ,zz9.99’)
AS LOWEST
,CAST (MIN (salary_amount) AS FORMAT ‘zz, ZZZ,zz9.99’)
AS br>,CAST (AVG (salary_amount) AS FORMAT ‘zz, ZZZ,zz9.99’)
AS _AVERAGE)
FROM employee
GROUP BY department_number
ORDER BY department_number; Since AVERAGE is itself a keyword, in the above example, it is preceded by an underscore
to distinguish it.
when grouping statistics on multiple fields, GROUP BY produces only one level of summary. Example
such as: for the department 401 and 403 according to the work code group statistics salaries.
SELECT department_number
,job_code
,SUM (salary_amount)
FROM employee
WHERE department_number IN (401, 403)
GROUP BY department_number, job_code
ORDER BY 1, 2;

results:
department_number job_code SUM (salary_amount)
401 411100 37850.00
401 412101 107825.00
401 412102 56800.00
401 413201 43100.00
403 431100 31200.00
403 432101 As you can see from this example, when there are multiple fields in GROUP BY, it can only produce a summary of level
, and the summary is made according to the last field (here is job_code).

GROUP BY and HAVING conditions
HAVING conditions clause is used together with GROUP to limit the result of grouping statistics to
and only return the grouping statistics that meet its conditions.
for example, show the number of people in the department, total salary, maximum salary in the department,
minimum salary and average salary in the department by department number order, if only show the department with average salary less than 36000.
SELECT department_number (TITLE ‘DEPT’)
,COUNT (*) (TITLE ‘#_EMPS’)
,SUM (salary_amount) (TITLE ‘TOTAL’)
(FORMAT ‘zz, ZZZ,zz9.99’)
,MAX (salary_amount) (TITLE ‘HIGHEST’)
(FORMAT ‘ ‘zz, ZZZ,zz9.99’)
,MIN (TITLE ‘amount)
(FORMAT ‘zz, ZZZ,zz9.99)
,AVG (TITLE ‘AVERAGE’)
(FORMAT ‘zz, ZZZ,zz9.99’)
FROM employee
GROUP BY department_number
HAVING AVG (salary_amount) < 36000;

result:
DEPT #_EMPS TOTAL b> 401 7 245,575.00 46,000.00 24,500.00 35,082.14

1, WHERE: data records are used to qualify the tables that participate in the grouping aggregation operation. Only
data records that meet the criteria are selected to participate in the grouping aggregation.
2, GROUP BY: to GROUP the records that meet the WHERE clause
3, HAVING: to qualify the GROUP aggregation results that can be returned
4, ORDER BY: to specify the output ORDER of the results

SQL Error: 0, SQLState: 08S01 & Communications link failure

Error:

WARN : org.hibernate.engine.jdbc.spi.SqlExceptionHelper - SQL Error: 0, SQLState: 08S01
ERROR: org.hibernate.engine.jdbc.spi.SqlExceptionHelper - Communications link failure

The data source configuration used initially is as follows

<bean id="dataSource"
          class="org.springframework.jdbc.datasource.DriverManagerDataSource">
<property name="driverClassName" value="com.mysql.jdbc.Driver"/>
<property name="url"
value="jdbc:mysql://localhost:3306/db_heybar01?useUnicode=true&amp;characterEncoding=UTF-8"/>
<property name="username" value="test"/>
<property name="password" value="test"/>

</bean>

Through the error message and the preliminary judgment of searching is that the number of database connections is not enough, try to change the connection pool:
modified data source configuration:

<bean id="dataSource"
          class="com.mchange.v2.c3p0.ComboPooledDataSource" destroy-method="close">
    <property name="driverClass">
        <value>com.mysql.jdbc.Driver</value>
    </property>
    <property name="jdbcUrl">
        <value>jdbc:mysql://101.201.73.167:3306/db_heybar01?useUnicode=true&amp;characterEncoding=UTF-8</value>
    </property>
    <property name="properties">
        <props>
            <prop key="c3p0.minPoolSize">2</prop>
            <prop key="c3p0.maxPoolSize">50</prop>
            <prop key="c3p0.timeout">5000</prop>
            <prop key="c3p0.max_statement">100</prop>
            <prop key="c3p0.testConnectionOnCheckout">true</prop>
            <prop key="user">nupa01</prop>
            <prop key="password">NUPA_mysql_2017</prop>
        </props>
    </property>
</bean>

How to Fix Error in module RSQL of the database interface

keywords
Error in module RSQL of the database interface error key: RFC_ERROR_SYSTEM_FAILUREdbtran ERROR (set_input_da_spec): statement too big[dbtran.c#4854] marker count = 18655 > max. marker count = 16000 [dbtran.c#4854] sap note:13607


Problem description
[Problem] After EP was tested by the development machine, the EP was executed after it was released to the production machine, and this Problem occurred:

Error message:
Error in module RSQL of the database interface, Error key: RFC_ERROR_SYSTEM_FAILURE
Problem analysis
You can first try the following operations:
1, check, test the RFC, and transfer the related requests to the production environment; 2. Reimport RFC in NWDS and republish the project (note that the operation of production environment release is different from that of development machine); 3. Restart EP;
if the problem is still unresolved, read on.
Check the ABAP Runtime Error log

through the transport code ST22. Double-click the corresponding Error log to enter the Runtime Error Long Text interface, where there are detailed Error reports.
Some of the error messages I picked:
Kategorie (category) : ABAP Programming Error
Laufzeitfehler (runtime Error) : DBIF_RSQL_INVALID_RSQL
Ausnahme (exception) : CX_SY_OPEN_SQL_DB
ABAP Programm: SAPLZEWM_RFC2
【Kurztext】 (German, meaning category)
Error in module RSQL of the database interface

Error in the ABAP Application Program
the current ABAP Program “SAPLZEWM_RFC2” had to be terminated because it has come across a statement that unfortunately cannot be executed.

An exception that is explained in detail below once again occurred.
The Exception, which is assigned to class ‘CX_SY_OPEN_SQL_DB’, was not caught in procedure “ZTM_RFC_YSQSD_GETORDER_V2” (FUNCTION) “, nor was it propagated by a RAISING clause.
Since the caller of the procedure could not have anticipated that the exception would occur, the current program is terminated.
The reason for the exception is:
The SQL statement generated from the SAP Open SQL statement violates a restriction imposed by the underlying database system of the ABAP system.
Possible error causes:
o The maximum size of an SQL statement was exceeded.
o The statement contains too many input variables.
o The input data requires more space than is available.
You can generally find details in the system log (SM21) and in the developer trace of the relevant work process (ST11).
Cause analysis,
1. In the ABAP Select statement, when range Table is used in the WHERE clause, the type of range Table exceeds the maximum limit of the database (the maximum value is determined by DB).
2. The source code location is already listed above the error message:

The solution
1. Search SAP Note: 13607. Extract the contents of Note


2. So I modified my code:

DATA r_so LIKE RANGE OF vbak-vbeln WITH HEADER LINE. 
DATA lines LIKE LINE OF r_so.
DESCRIBE TABLE r_so LINES lines.
IF lines EQ 0.
    SELECT
      vbak~vbeln AS vbeln
      adrc~name1 AS name1 
      vbpa~kunnr AS kunnr
      vbpa~parvw AS parvw
      adrc~city1 AS city1
      FROM vbpa
      INNER JOIN vbak ON vbak~vbeln EQ vbpa~vbeln
      INNER JOIN adrc ON vbpa~adrnr EQ adrc~addrnumber
      INTO CORRESPONDING FIELDS OF TABLE gt_display_vbpa_ag
      WHERE adrc~name1 IN r_shippername 
        AND vbpa~kunnr IN r_shipper     
        AND vbpa~parvw EQ 'AG'.
...
ELSE.
    TRY.
      SELECT
         vbak~vbeln AS vbeln
         adrc~name1 AS name1
         vbpa~kunnr AS kunnr
         vbpa~parvw AS parvw
         adrc~city1 AS city1
         FROM vbpa
         INNER JOIN vbak ON vbak~vbeln EQ vbpa~vbeln
         INNER JOIN adrc ON vbpa~adrnr EQ adrc~addrnumber
         INTO CORRESPONDING FIELDS OF TABLE gt_display_vbpa_ag
         FOR ALL ENTRIES IN r_so 
         WHERE vbak~vbeln EQ r_so-low
           AND adrc~name1 IN r_shippername 
           AND vbpa~kunnr IN r_shipper     
           AND vbpa~parvw EQ 'AG'.

   CATCH cx_sy_open_sql_db.
   ENDTRY.
...
ENDIF.

3. After modifying the RFC, it is necessary to re-import Model
in WD4J
4. Re-transmit the Request to production and re-publish it to EP. Problem solved
Summarize the ideas for solving THE SAP problem
1, do not do hand party, do not ask a mistake, be sure to read the error message, analysis of the possible part of the error, is RFC error or WD4J error; 2. Error messages can be viewed through Tcode ST22 or ST11 or sm21; 3. About search engines:
SAP search: http://search.sap.com/ (this SAP note the number 13607 is found in the above) SAP note: https://websmp206.sap-ag.de/NOTES (search keywords are provided in the error log)

SAP custom Google search engine, https://cse.google.com/cse/home?cx=013447253335410278659:k8ob9ipscwg

JDBC connect to Sql Server to connect to the database–The TCP/IP connection to the host localhost, port 1433 has failed

Have you ever made such a mistake?

The TCP/IP connection to the host localhost, port 1433 has failed.

com.microsoft.sqlserver.jdbc.SQLServerException: 
The TCP/IP connection to the host localhost, port 1433 has failed. Error: "Connection refused: connect. 
Verify the connection properties.
Make sure that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port. 
Make sure that TCP connections to the port are not blocked by a firewall.".

Solutions:
1. Select the computer – & GT; Right click management – & GT; Computer management — & GT; Service and application
(1) first check SQL server service whether
has been enabled to — > SQL Server configuration Manager — & GT; SQL Server service, make sure local SQL Server service is enabled.

(2) then check SQL server network configuration
to — > SQL Server configuration Manager — & GT; SQL Server network configuration ensures that the Named Pipes and TCP/IP protocols are enabled.


2. If we run the program again, it may appear that the connection is still unsuccessful, so we can continue to solve the problem:
or code> SQL server network configuration
to — > SQL Server configuration Manager — & GT; SQL Server network configuration, Named Pipes and TCP/IP protocol is enabled, select TCP/IP right click – > Property – & gt; IP address, scroll down to see if IPALL in TCP port is 1433, no, then change to 1433.

finally, restart SQL Server service, then run the program again, successful, comfortable!

[solved] sql30082n security processing failed with reason “24” (“user name and / or password invalid”)

login when the following problems occur:

Could not connect to DB: SQLSTATE[08001] SQLConnect: -30082 [IBM][CLI Driver] SQL30082N  Security processing
 failed with reason "24" ("USERNAME AND/OR PASSWORD INVALID").  SQLSTATE=08001

check the relevant solutions:

http://www-01.ibm.com/support/docview.wss?uid=swg21327771
http://www-01.ibm.com/support/docview.wss?uid=swg21416382

and look for the error code on the command line:

[db2inst1@xxx ~]$ db2 ?sql30082N

SQL30082N  Security processing failed with reason "<reason-code>"
      ("<reason-string>").

Explanation: 

An error occurred during security processing. The cause of the security
error is described by the "<reason-code>" and corresponding
"<reason-string>" value.

The following is a list of reason codes and corresponding reason
strings:

0 (NOT SPECIFIED)
         

         The specific security error is not specified.


1 (PASSWORD EXPIRED)
         

         The password specified in the request has expired.


2 (PASSWORD INVALID)
         

         The password specified in the request is not valid.


3 (PASSWORD MISSING)
         

         The request did not include a password.


4 (PROTOCOL VIOLATION)
         

         The request violated security protocols.


5 (USERID MISSING)
         

         The request did not include a userid.


6 (USERID INVALID)
         

         The userid specified in the request is not valid.


7 (USERID REVOKED)
         

         The userid specified in the request has been revoked.


8 (GROUP INVALID)
         

         The group specified in the request is not valid.


9 (USERID REVOKED IN GROUP)
         

         The userid specified in the request has been revoked in the
         group.


10 (USERID NOT IN GROUP)
         

         The userid specified in the request is not in the group.


11 (USERID NOT AUTHORIZED AT REMOTE LU)
         

         The userid specified in the request is not authorized at the
         remote Logical Unit.


12 (USERID NOT AUTHORIZED FROM LOCAL LU)
         

         The userid specified in the request is not authorized at the
         remote Logical Unit when coming from the local Logical Unit.


13 (USERID NOT AUTHORIZED TO TP)
         

         The userid specified in the request is not authorized to access
         the Transaction Program.


14 (INSTALLATION EXIT FAILED)
         

         The installation exit failed.


15 (PROCESSING FAILURE)
         

         Security processing at the server failed.


16 (NEW PASSWORD INVALID)
         

         the password specified on a change password request did not
         meet the server's requirements.


17 (UNSUPPORTED FUNCTION)
         

         the security mechanism specified by the client is invalid for
         this server. Some typical examples:

          
         *  The client sent a new password value to a server that does
            not support the change password function.
         *  The client sent SERVER_ENCRYPT authentication information to
            a server that does not support password encryption.
            Authentication type catalog information must be the same at
            the server and the client.
         *  The client sent a userid (but no password) to a server that
            does not support authentication by userid only.
         *  The client has not specified an authentication type, and the
            server has not responded with a supported type. This might
            include the server returning multiple types from which the
            client is unable to choose.
         *  The CLIENT AUTHENTICATION type is not supported by "IBM Data
            Server Driver for ODBC and CLI" and "IBM Data Server Driver
            package"


18 (NAMED PIPE ACCESS DENIED)
         

         The named pipe is inaccessible due to a security violation.


19 (USERID DISABLED or RESTRICTED)
         

         The userid has been disabled, or the userid has been restricted
         from accessing the operating environment at this time.


20 (MUTUAL AUTHENTICATION FAILED)
         

         The server being contacted failed to pass a mutual
         authentication check. The server is either an imposter, or the
         ticket sent back was damaged.


21 (RESOURCE TEMPORARILY UNAVAILABLE)
         

         Security processing at the server was terminated because a
         resource was temporarily unavailable. For example, on AIX, no
         user licenses may have been available.


<strong>24 (USERNAME AND/OR PASSWORD INVALID)
         

         The username specified, password specified, or both, are
         invalid. Some specific causes are:

          
         1. If you have recently changed permissions on DB2 critical
            files such as db2ckpw or moved to a new Fixpak, the db2iupdt
            command which updates the instance might not have been run.
         2. The username being used might be in an invalid format. For
            example, on UNIX and Linux platforms, usernames must be all
            be lowercase.
         3. An error might have been made in specifying the catalog
            information. For example, the correct authentication type
            might not have been specified or, if applicable, the remote
            server might not have been cataloged on the local system.</strong>


25 (CONNECTION DISALLOWED)
         

         The security plugin has disallowed the connection.


26 (UNEXPECTED SERVER ERROR)
         

         The server security plugin encountered an unexpected error. The
         administration notification log file on the server contains
         more specific problem information. The following are examples
         of issues that can cause problems:

          
         *  The security service was not started.
         *  The userid starting the DB2 service did not have admin
            privileges.


27 (INVALID SERVER CREDENTIAL)
         

         The server security plugin encountered an invalid server
         credential.


28 (EXPIRED SERVER CREDENTIAL)
         

         The server security plugin encountered an expired server
         credential.


29 (INVALID CLIENT SECURITY TOKEN)
         

         The server security plugin encountered an invalid security
         token sent by the client.


30 (CLIENT PLUGIN MISSING API)
         

         The client security plugin is missing a required API.


31 (WRONG CLIENT PLUGIN TYPE)
         

         The client security plugin is of the wrong plugin type.


32 (UNKNOWN CLIENT GSS-API PLUGIN)
         

         The client security plugin does not have a matching GSS-API
         security plugin available for connection to the database.


33 (UNABLE TO LOAD CLIENT PLUGIN)
         

         The client security plugin cannot be loaded.


34 (INVALID CLIENT PLUGIN NAME)
         

         The client security plugin name is invalid.


35 (INCOMPATIBLE CLIENT PLUGIN API VERSION)
         

         The client security plugin reports an API version that is
         incompatible with DB2.


36 (UNEXPECTED CLIENT ERROR)
         

         The client security plugin encountered an unexpected error.


37 (INVALID SERVER PRINCIPAL NAME)
         

         The server security plugin encountered an invalid principal
         name.


38 (INVALID CLIENT CREDENTIAL)
         

         The client security plugin encountered an invalid client
         credential.


39 (EXPIRED CLIENT CREDENTIAL)
         

         The client security plugin encountered an expired client
         credential.


40 (INVALID SERVER SECURITY TOKEN)
         

         The client security plugin encountered an invalid security
         token sent by the server.


41 (SWITCH USER INVALID)
         

         The client is configured to request a trusted connection and
         switch user in the trusted connection. A trusted connection was
         not established and so the switch user request is invalid.


42 (ROOT CAPABILITY REQUIRED)
         

         Authentication using local client or server passwords is not
         currently enabled.


43 (NON-DB2 QUERY MANAGER PRODUCT DISALLOWED CONNECTION)
         

         A non-DB2 query manager product has disallowed the connection.

User response: 

Ensure that the proper userid and/or password is supplied.

The userid may be disabled, the userid may be restricted to accessing
specific workstations, or the userid may be restricted to certain hours
of operation.

17       

         Retry the command with a supported authentication type. Ensure
         that catalog information specifies the correct authentication
         type.


20       

         Make sure the authentication mechanism for the server is
         started, and retry.


<strong>24       

         Solutions to specific problem causes described previously in
         this message are:

          
         1. Run DB2IUPDT <InstName> to update the instance.
         2. Ensure that the username created is valid. Review the DB2
            General Naming Rules.
         3. Ensure that catalog information is correct.</strong>


25       

         Change the database name used for the connection or the TCP/IP
         address used to connect to this database.


26       

         Fix the problem identified by the plugin error message text in
         the administration notification log.

          

         If you are unable to correct the problem, invoke the
         Independant Trace Facility and retry the scenario to collect
         information for IBM support.


27       

         Verify that the server credential is provided during security
         plugin initialization and that it is in a format recognized by
         the security plugin. As the credential will be used to accept
         contexts, it must be an ACCEPT or BOTH credential.


28       

         Contact your DBA. The server's credential must be renewed
         before the command is resubmitted. If renewing alters the
         credential handle, then a db2stop and db2start will be
         necessary. For information on how to renew your server's
         credential, consult the documentation available for the
         authentication mechanism used by the security plugin.


29       

         Resubmit the statement. If the problem still exists, then
         verify that the client security plugin is generating a valid
         security token.


30       

         Check the administration notification log file for the name of
         the required missing API. Add the missing API to the security
         plugin.


31       

         Specify the right type of security plugin in the appropriate
         database manager configuration parameter. For example, do not
         specify a userid-password based security plugin for the
         SRVCON_GSSPLUGIN_LIST database manager configuration parameter.


32       

         Install the matching security plugin that the database server
         used on the client. Ensure that the indicated security plugin
         is located in the client-plugin directory.


33       

         Check the administration notification log file on the client
         for more information. Fix the problem identified by the error
         message text in the administration notification log.


34       

         Specify a valid security plugin name. The name should not
         contain any directory path information.


35       

         Ensure that the security plugin is using a supported version of
         the APIs and that it is reporting a correct version number.


36       

         Check the administration notification log file on the client
         for more information. Fix the problem identified by the error
         message text in the administration notification log.


37       

         Check the administration notification log file for the
         principal name. Make sure the principal name is in a format
         that is recognized by the security plugin.


38       

         Verify that the client credential (generated by
         db2secGenerateInitialCred or provided as an inbound delegated
         credential) is in a format recognized by the security plugin.
         As the credential will be used to initiate contexts, it must be
         an INITIATE or BOTH credential.


39       

         The user issuing the statement must obtain the appropriate
         credentials (or re-obtain their initial credentials) and then
         resubmit the statement.


40       

         Resubmit the statement. If the problem still exists, then
         verify that the server security plugin is generating a valid
         security token.


41       

         Re-establish a trusted connection with valid credentials and
         re-submit a switch user request.


42       

         To enable local client or server authentication for non-root
         installations, the system administrator must run the db2rfe
         script. Alternatively, authentication can be done using a
         security plugin.


43       

         If additional explanation is required, contact your
         administrator for the query manager product.

sqlcode: -30082

sqlstate: 08001


   Related information:
   Security plug-in API versioning
   Authentication
   Security plug-ins

seems to be useless until finally, the original code about database connection ini file, db2inst1 was incorrectly written as db2instl – – no words

notice 1 and l, ok, flip the table!