How to solve SQL1009N

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

James - 22 Dec 2006 03:29 GMT

Please ran the following commands as below. (databae is V8 fix 11 on
AIX)
1.db2 connect to DBNAME user db2inst3 using XXX
2.db2 get db cfg
Then receive an error: SQL1009N The command is not valid.

I can run "db2 list tables". What I concern is why I can not run "get
db cfg" command? I checked the database directory, that's ok. I found
the database was in inconsistent status when I ran db2dart tool.

Any advice?

Thank you so much!

James

Reply to this Message

Pierre Saint-Jacques - 22 Dec 2006 04:06 GMT

The command should be
db2 get db cfg for DBNAME
Do following, for this or any other message:
db2 ? sql1009n

D:\SQLLIB\BIN>db2 ? sql1009n

SQL1009N The command is not valid.

Explanation:

The command is not supported when issued on a client-only
workstation or against remote databases. An example of such a
command is cataloging a local database.

The command cannot be processed.

User Response:

Possible solutions include:

o Issue the specified command from a non client-only
workstation or from the workstation where the database
resides.

o Verify that the database is cataloged correctly.

o Issue a different command.

Regards, Pierre.

Signature

Pierre Saint-Jacques
SES Consultants Inc.
514-737-4515

> Please ran the following commands as below. (databae is V8 fix 11 on
> AIX)
[quoted text clipped - 11 lines]
>
> James

Reply to this Message

James - 22 Dec 2006 15:27 GMT

Thanks.
1.When I connect to database, I can run "get db cfg" directly, need not
run "get db cfg for xxx"
2.I knew the meaning of SQL1009N. My question is why I can connect to
database and perform import, export and SQL statements and so on, just
failed on command "get db cfg" or "get db cfg for xxx". Just due to
catalog issue?

On Dec 22, 12:06 pm, "Pierre Saint-Jacques" <sesc...@invalid.net>
wrote:

> The command should be
> db2 get db cfg for DBNAME
[quoted text clipped - 49 lines]
>
> > James- Hide quoted text -- Show quoted text -

Reply to this Message

Pierre Saint-Jacques - 22 Dec 2006 17:26 GMT

Apologies for false presumptions of mine.

I think that because you are connected, the command gives you the db cfg of
what you are connected to. When no connect is given, then you have to
specify the dbname in the command, since db2 has no clue to which cfg of
many db's need to be retrieved.

Now if that fails with the name specified, it's another issue. In that
case, even if the db name is given, it means that the db is remote. GET DB
CFG is an instance level command and therefore requires attachment to the
instance owning the db: attach to <nodename> user ... using ...

HTH, Pierre.

Signature

Pierre Saint-Jacques
SES Consultants Inc.
514-737-4515

> The command should be
> db2 get db cfg for DBNAME
[quoted text clipped - 49 lines]
>
> > James- Hide quoted text -- Show quoted text -

Reply to this Message

James - 23 Dec 2006 02:45 GMT

Thanks for your reply.

> Apologies for false presumptions of mine.
>
[quoted text clipped - 77 lines]
> >
> > > James- Hide quoted text -- Show quoted text -

Reply to this Message