I installed DB2 V8.2 ESE on my desktop, after removing my V9.5
client. I rebooted my desktop a number of times in the process. When
the install finished, it gave me an option to create a new database.
I choose that option. During the database creation process I got the
error below. I don't know why this is happening. It's creating a new
database (the first) in the instance. I'm not trying to load an older
backup. Any ideas? Is there some other DB2 V9.5 client software I
need to remove? I looked in "Add/Remove Programs" and don't see
anything that's 'obviously' DB2 V9.

Thanks.


SQL1091C The release number of the database is not valid.

Explanation:

The release number of the database is not compatible with the
release number of the installed version of the database manager.
This can be the release number when the database was created, the
release number when the database was last migrated, or the
highest version, release, modification, and fixpak level defined
in the catalog.

The command cannot be processed. If the error occurred during a
Migrate or Restore, you are attempting to migrate or restore an
incompatible release of database. If the error occurred on the
first connection after removing a fixpak, you are attempting to
connect to a database that is defined to use a higher level of
database manager code.

User Response:

Use only databases created with a compatible release of database
manager. If the error occurred during a Migrate or Restore, you
must first migrate the database to a release which can be
migrated by the current release of the database manager. If the
error occurred on the first connection after removing a fixpak,
the database should be restored from a backup prior to using the
utility to update the database to the fixpak level.

sqlcode : -1091

sqlstate : 08004

I installed the latest V8 version on IBM's website (FP18)

I've stopped and started the instance

When I run db2level, I get

DB21085I Instance "DB2" uses "32" bits and DB2 code release
"SQL08029" with level identifier "030A0106".
Informational tokens are "DB2 v8.1.18.980", "s090715", "WR21443", and
FixPak "18".
Product is installed at "D:\PROGRA~1\IBM\SQLLIB".

Here's the output when I try creating a database at the command line

db2 create db test
SQL1091C The release number of the database is not valid.
SQLSTATE=08004

Here's the output from db2 get dbm cfg




db2 get dbm cfg

Database Manager Configuration

Node type = Enterprise Server Edition with local and remote
clients

Database manager configuration release level = 0x0a00

Maximum total of files open (MAXTOTFILOP) = 16000
CPU speed (millisec/instruction) (CPUSPEED) =
6.612819e-007
Communications bandwidth (MB/sec) (COMM_BANDWIDTH) = 1.000000e
+002

Max number of concurrently active databases (NUMDB) = 8
Data Links support (DATALINKS) = NO
Federated Database System Support (FEDERATED) = NO
Transaction processor monitor name (TP_MON_NAME) =

Default charge-back account (DFT_ACCOUNT_STR) =

Java Development Kit installation path (JDK_PATH) = D:
\PROGRA~1\IBM\SQLLI
B\java\jdk

Diagnostic error capture level (DIAGLEVEL) = 3
Notify Level (NOTIFYLEVEL) = 3
Diagnostic data directory path (DIAGPATH) =

Default database monitor switches
Buffer pool (DFT_MON_BUFPOOL) = OFF
Lock (DFT_MON_LOCK) = OFF
Sort (DFT_MON_SORT) = OFF
Statement (DFT_MON_STMT) = OFF
Table (DFT_MON_TABLE) = OFF
Timestamp (DFT_MON_TIMESTAMP) = ON
Unit of work (DFT_MON_UOW) = OFF
Monitor health of instance and databases (HEALTH_MON) = ON

SYSADM group name (SYSADM_GROUP) =
SYSCTRL group name (SYSCTRL_GROUP) =
SYSMAINT group name (SYSMAINT_GROUP) =
SYSMON group name (SYSMON_GROUP) =

Client Userid-Password Plugin (CLNT_PW_PLUGIN) =
Client Kerberos Plugin (CLNT_KRB_PLUGIN) = IBMkrb5
Group Plugin (GROUP_PLUGIN) =
GSS Plugin for Local Authorization (LOCAL_GSSPLUGIN) =
Server Plugin Mode (SRV_PLUGIN_MODE) = UNFENCED
Server List of GSS Plugins (SRVCON_GSSPLUGIN_LIST) =
Server Userid-Password Plugin (SRVCON_PW_PLUGIN) =
Server Connection Authentication (SRVCON_AUTH) =
NOT_SPECIFIED
Database manager authentication (AUTHENTICATION) = SERVER
Cataloging allowed without authority (CATALOG_NOAUTH) = NO
Trust all clients (TRUST_ALLCLNTS) = YES
Trusted client authentication (TRUST_CLNTAUTH) = CLIENT
Bypass federated authentication (FED_NOAUTH) = NO

Default database path (DFTDBPATH) = D:

Database monitor heap size (4KB) (MON_HEAP_SZ) = 66
Java Virtual Machine heap size (4KB) (JAVA_HEAP_SZ) = 512
Audit buffer size (4KB) (AUDIT_BUF_SZ) = 0
Size of instance shared memory (4KB) (INSTANCE_MEMORY) = AUTOMATIC
Backup buffer default size (4KB) (BACKBUFSZ) = 1024
Restore buffer default size (4KB) (RESTBUFSZ) = 1024

Agent stack size (AGENT_STACK_SZ) = 16
Minimum committed private memory (4KB) (MIN_PRIV_MEM) = 32
Private memory threshold (4KB) (PRIV_MEM_THRESH) = 20000

Sort heap threshold (4KB) (SHEAPTHRES) = 10000

Directory cache support (DIR_CACHE) = YES

Application support layer heap size (4KB) (ASLHEAPSZ) = 15
Max requester I/O block size (bytes) (RQRIOBLK) = 32767
DOS requester I/O block size (bytes) (DOS_RQRIOBLK) = 4096
Query heap size (4KB) (QUERY_HEAP_SZ) = 1000

Workload impact by throttled utilities(UTIL_IMPACT_LIM) = 10

Priority of agents (AGENTPRI) = SYSTEM
Max number of existing agents (MAXAGENTS) = 400
Agent pool size (NUM_POOLAGENTS) =
200(calculated)
Initial number of agents in pool (NUM_INITAGENTS) = 0
Max number of coordinating agents (MAX_COORDAGENTS) = MAXAGENTS
Max no. of concurrent coordinating agents (MAXCAGENTS) =
MAX_COORDAGENTS
Max number of client connections (MAX_CONNECTIONS) =
MAX_COORDAGENTS

Keep fenced process (KEEPFENCED) = YES
Number of pooled fenced processes (FENCED_POOL) =
MAX_COORDAGENTS
Initial number of fenced processes (NUM_INITFENCED) = 0

Index re-creation time and redo index build (INDEXREC) = RESTART

Transaction manager database name (TM_DATABASE) = 1ST_CONN
Transaction resync interval (sec) (RESYNC_INTERVAL) = 180

SPM name (SPM_NAME) = LRMCGORM
SPM log size (SPM_LOG_FILE_SZ) = 256
SPM resync agent limit (SPM_MAX_RESYNC) = 20
SPM log path (SPM_LOG_PATH) =

NetBIOS Workstation name (NNAME) =

TCP/IP Service name (SVCENAME) = db2c_DB2
Discovery mode (DISCOVER) = SEARCH
Discover server instance (DISCOVER_INST) = ENABLE

Maximum query degree of parallelism (MAX_QUERYDEGREE) = ANY
Enable intra-partition parallelism (INTRA_PARALLEL) = NO

No. of int. communication buffers(4KB)(FCM_NUM_BUFFERS) = 4096
Number of FCM request blocks (FCM_NUM_RQB) = AUTOMATIC
Number of FCM connection entries (FCM_NUM_CONNECT) = AUTOMATIC
Number of FCM message anchors (FCM_NUM_ANCHORS) = AUTOMATIC

Node connection elapse time (sec) (CONN_ELAPSE) = 10
Max number of node connection retries (MAX_CONNRETRIES) = 5
Max time difference between nodes (min) (MAX_TIME_DIFF) = 60

db2start/db2stop timeout (min) (START_STOP_TIME) = 10

Finally abandon trying to get V8 running on a system that V9.x had
been installed on.

On Oct 22, 3:27*pm, Richard <rmcgor... (AT) gmail (DOT) com> wrote:
I would guess that your problem is that the database directory is
still the DB2 v9.5 format and is not compatible with the DB2 v8.x
format. Removing the database directory after removing DB2 v9.5 may
resolve this issue.