Topic
  • 7 replies
  • Latest Post - ‏2012-12-02T04:57:07Z by SystemAdmin
d91
d91
6 Posts

Pinned topic database could not be found

‏2012-01-29T23:58:10Z |
Hi,

I have almost zero exposure on DB2, let along DB2 admin. Now, I've restored a database from somewhere else into my DB2 environment. But when I tried to use it, I get the following error:


$ db2 connect to mydb1 SQL0901N  The SQL statement failed because of a non-severe system error. Subsequent SQL statements can be processed.  (Reason 
"Scan interface error".) SQLSTATE=58004


What does it mean? How should I fix it?

FYI, here is how I restored the database before that:


$ db2 restore db mydb1 from /path/to/mydb1-bak DB20000I  The RESTORE DATABASE command completed successfully.
Updated on 2012-12-02T04:57:07Z at 2012-12-02T04:57:07Z by SystemAdmin
  • d91
    d91
    6 Posts

    Re: database could not be found

    ‏2012-01-30T00:02:13Z  
    I can't edit my own post?

    Anyway, please rename my OP to "restore a database" which is a more proper title.

    Thanks
  • SystemAdmin
    SystemAdmin
    5837 Posts

    Re: database could not be found

    ‏2012-01-30T16:24:13Z  
    • d91
    • ‏2012-01-30T00:02:13Z
    I can't edit my own post?

    Anyway, please rename my OP to "restore a database" which is a more proper title.

    Thanks
    was the backup taken on a newer db2 instance?
  • d91
    d91
    6 Posts

    Re: database could not be found

    ‏2012-02-07T17:46:47Z  
    was the backup taken on a newer db2 instance?
    Thanks momi,

    That might be actually true, but I'm really not sure.
    I can't access the original system for the moment, will get back to you on this.

    Thanks
  • d91
    d91
    6 Posts

    Re: database could not be found

    ‏2012-02-07T17:48:07Z  
    I can't access the original system for the moment to give the answer, will get back and reopen this.
  • d91
    d91
    6 Posts

    Re: database could not be found

    ‏2012-02-07T17:52:29Z  
    • d91
    • ‏2012-01-30T00:02:13Z
    I can't edit my own post?

    Anyway, please rename my OP to "restore a database" which is a more proper title.

    Thanks
    > d91 wrote:
    > Anyway, please rename my OP to "restore a database" which is a more proper title.

    Hmm... found out that I posted to the wrong forum as well. Maybe "DB2 Application Development"? but definitely not DB2 Express.

    Can somebody help?
    Sorry about that.

    Thanks
  • d91
    d91
    6 Posts

    Re: database could not be found

    ‏2012-02-07T17:55:14Z  
    • d91
    • ‏2012-02-07T17:52:29Z
    > d91 wrote:
    > Anyway, please rename my OP to "restore a database" which is a more proper title.

    Hmm... found out that I posted to the wrong forum as well. Maybe "DB2 Application Development"? but definitely not DB2 Express.

    Can somebody help?
    Sorry about that.

    Thanks
    > d91 wrote:
    > Maybe "DB2 Application Development"?

    Seems "IBM DB2 9 forum" is more appropriate.

    thanks
  • SystemAdmin
    SystemAdmin
    5837 Posts

    Re: database not accessible

    ‏2012-12-02T04:57:07Z  
    • d91
    • ‏2012-01-30T00:02:13Z
    I can't edit my own post?

    Anyway, please rename my OP to "restore a database" which is a more proper title.

    Thanks
    Not bale to access database and tables getting below error.
    IBMCLI Driver SQL0901N The SQL statement failed because of a
    non-severe system error. Subsequent SQL statements can be
    processed. (Reason "Scan interface error".) SQLSTATE=58004

    Explanation:

    An error has occurred which is due to a system error. Processing of the
    SQL statement has ended for reason "<reason>" (this is in English only
    and is useful only to IBM support personnel).

    User response:

    Record the message number (SQLCODE) and reason "<reason>".

    If trace was active, invoke the Independent Trace Facility at the
    operating system command prompt. Then contact your technical service
    representative with the following information:

    • Problem description
    • SQLCODE
    • reason "<reason>"
    • SQLCA contents if possible
    • Trace file if possible.

    Federated system users: isolate the problem to the data source failing
    the request (refer to the Troubleshooting Guide to determine which data
    source is failing to process the SQL statement) and take the necessary
    diagnostic steps for that data source. The problem determination
    procedures for data sources vary, so refer to the applicable data source
    manuals.

    sqlcode: -901

    sqlstate: 58004, 5UA0L