If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > Database Server Software > DB2 > Cannot use db after FP 13 install!!!

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 12-04-06, 11:09
brdholman brdholman is offline
Registered User
 
Join Date: Nov 2006
Posts: 19
Exclamation Cannot use db after FP 13 install!!!

Sun Solaris, UDB v8.1, fp 10.

I've done the following:
./installFixPak13 -y -> successful
./db2iupdt -e -> successful
db2start -> successful

then got following:
1st server>>
t01epp1t:/ # db2 connect to t01epprt
SQL1013N The database alias name or database name "" could not be found.
SQLSTATE=42705

2nd server>>
db2 force application all
SQL1001N "" is not a valid database name. SQLSTATE=2E000

All of my databases are now down. Does ANYONE know what causes this situation and how to fix it?

thanks,
jholman
Reply With Quote
  #2 (permalink)  
Old 12-04-06, 11:24
brdholman brdholman is offline
Registered User
 
Join Date: Nov 2006
Posts: 19
Install said successful, but not all packages installed. I am reinstalling now.
Reply With Quote
  #3 (permalink)  
Old 12-19-06, 12:53
Supermann Supermann is offline
Registered User
 
Join Date: Dec 2006
Posts: 1
Hi brdholman,

did you solve your problem regarding to this issue,
<-
t01epp1t:/ # db2 connect to t01epprt
SQL1013N The database alias name or database name "" could not be found.
SQLSTATE=42705
->

I have exactly the same issue with FP 13,
thank you in advance
Regards,
Suparmann
Reply With Quote
  #4 (permalink)  
Old 12-19-06, 13:03
brdholman brdholman is offline
Registered User
 
Join Date: Nov 2006
Posts: 19
Yes I did. I should have posted that back. Sorry.

Two things were wrong according to IBM. The first one may or may not have had something to do with it.
1. Make sure to kill ALL db2 processes before updating the instance.
2. When I applied FixPak 10, right after the initial install, I used 'db2iupdt -d'. I was told to use 'db2iupdt -u <fencename> <instname>' or 'db2iupdt -u <instname> <instname>'. Then log into a new session as the instance, do a db2level to confirm, then db2start from there.

After that it was fine.
Do be sure to rebind the db2 utilities in this directory:
$HOME/sqllib/bnd/bind
"db2 bind @db2ubind.lst blocking all grant public action REPLACE"
Do not use 'action add' or it doesn't work properly as I found out.

Hope this helps,
jholman
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On