Community archive

Ask something
Discussion Locked

DB2/UDB AIX - Administrative Server

0 helpful
6 replies

by fxhutch

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

the administration server/instance failed and I had to re-create it. I lostremote / ODBC connection to our DB2/6000 6.1.0 database on RS6000/AIX server. I have been getting the following errors when I try to connect through ODBC or the Client Configuration assistance:
SQL1046N The authorization ID is not valid SQLSTATE=28000
SQL1402N Unable to authenticate user due to unexpected system error.

Is there a way to successfully - manually create the administrative server.

6 replies

by kgosnell

Try pinging from both directions, perhaps it will show the address alteration, otherwise you will have to contact MS support to walk you through it, but on a hunch, if you are going through a dedicatd server outside of your influence, contact the ISP and have one of their techs attempt to resolve the issue , as they have a narrow protocol perhaps outside of the address range you are attempting to use. The Gateway protocol extends to areas that are not user controllable , and not just the E-mail.
I don't have much experiance in your area , but there are certain rigid protocols that are utilized throughout the Microsoft setup.
Hope you resolve it.

by fxhutch

The answer is not a Microsoft solution, this is DB2/IBM. Prior to the lost of the administrative server, we were able to address the database through ODBC connection. Some protocol which is established during setup is missing, and nothing pointsto this when you try to rebuild the administrative server.

by james_randy

If you are still tackling this problem, perhaps you should consider calling your local super-hero.

by maxwell edison

Greetings,

SQL1046N The authorization ID is not valid.

Cause: The authorization specified at logon is not valid for either the data source or the database manager. One of the following occurred:

The authorization contains more than 8 characters.

The authorization contains characters not valid for an authorization.

Valid characters are A through Z, a through z, 0 through 9, #, @ and $.

The authorization is PUBLIC or public.

The authorization begins with SYS, sys, IBM, ibm, SQL or sql.

The authorization violates some data source-specific naming convention.

The command cannot be processed.

Action: Log on with a valid authorization ID.

--------------------------------------------

SQL1402N Unable to authenticate user due to unexpected system error.

Cause: Call your system administrator. On unix-based systems, the file db2ckpw may not have the correct permission bits set, or the system may have run out of swap/paging space. On Windows NT, the DB2 security service may not have been started.

The command can not be processed.

DataJoiner users: this situation can be detected by DataJoiner or by the data source.

Action: On unix-based systems, have the system administrator ensure the correct access permissions are set for db2ckpw, and that there is enough swap/paging space allocated. On Windows NT, have the system administrator verify that the DB2 security service is installed and started.

Good luck,

Maxwell

by fxhutch

Your response was in my top 5 lists to resolve my problem.
Neither worked. I've had tried a series of possible solutions short of re-installing the DBMS but I had had no success. I have since upgraded the DBMS to v7.2 and everything is fine, but the problem still nags me. Others that I talked to who had experience the same problem sought re-installation as their solution, I was hopping for a less server answer.

This discussion is closed to new replies.