erreure mineure à l'installation de DB2

[anek971]

Bonjour à tous,

Je tente d'installer DB2 V9.1 sur un pc tournant avec l'OS Red Hat 5 32-bit en mode wizard,qui ne fonctionne pas totalement.
Ma démarche je lance le mode wizard en lancant ./db2setup.
J'ai donc une fenetre qui s'ouvre, j'accepte la licence.
Je choisit l'installation typique.
Je laisse le répertoire d'installatio par défaut.
Je choisis de créer l'instance DB2.
Je choisis Single partition instance.
Pour les comptes :
New instances:
Instance name: db2inst1
Start instance on reboot: Yes
Instance user information:
User name: db2inst1
Group name: db2grp1
Home directory: /home/db2inst1
Fenced user information:
User name: db2fenc1
Group name: db2fgrp1
Home directory: /home/db2fenc1

DB2 Administration server:
Instance user information:
User name: dasusr1
Group name: dasadm1
Home directory: /home/dasusr1

Mais j'ai continuellement le probleme suivant dans les fichiers logs, car j'ai essayé plusieurs fois de ré-installer ce dernier :

 
     Checking license agreement acceptance:.......Success
  Installing DB2 file sets:.......Success
  Setting DB2 library path:.......Success
  Executing control tasks:.......Success
  Updating global registry:.......Success
  Starting DB2 Fault Monitor:.......Success
  Updating the db2ls link:.......Success
  Registering DB2 licenses:.......Success
  Setting DEFAULT global profile registry VARIABLES:.......Success
  Creating the DB2 Administration Server:.......Failure
  Initializing instance list:.......Success
  Configuring DB2 instances:.......Failure
  Configuring the DB2 Administration Server:.......Failure
  Updating global profile registry:.......Success
   
  ============================================================
   
  DB2 Setup log file started at: Mon Nov 10 10:45:42 2008 CET
  ============================================================
   
  Operating system information: Linux 2.6.18-53.el5.#1 SMP Wed Oct 10 16:34:02 EDT 2007 i686
  Product TO install:                        DB2 Enterprise Server Edition
  Installation type:                         Typical
  Previously Installed Components:        
  Selected Components:                    
      GSKit support                          
      Product Messages - English             
      Base client support                    
      IBM Software Development Kit (SDK) FOR Java(TM)   
      Java Help (HTML) - English             
      Replication WITH MQ Server             
      Run-time Environment                   
      Java support                           
      SQL procedures                         
      ICU Utilities                          
      SQL Replication Support                
      Java Common files                      
      Base server support                    
      Control Center Help (HTML) - English   
      Connect support                        
      Configuration Assistant                
      Spatial Extender client                
      Base application development tools     
      Administration Server                  
      Communication support - TCP/IP         
      Control Center                         
      Parallel Extension                     
      Replication tools                      
      DB2 DATA source support                
      DB2 LDAP support                       
      DB2 Instance Setup wizard              
      First Steps                            
      DB2 Web Tools                          
      Product Signature FOR DB2 Enterprise Server Edition   
      XML Extender samples                   
      ADT sample programs                    
      Sample DATABASE source                 
      Spatial Extender samples               
  Languages:                              
      English                                
          ALL Products                       
  Target directory:                          /opt/ibm/db2/V9.1_01
                                          
  Space required:                            461 MB
                                          
  New instances:                          
      Instance name:                         db2inst1
          Start instance ON reboot:          Yes
          Instance user information:         
              User name:                     db2inst1
              GROUP name:                    db2grp1
              Home directory:                /home/db2inst1
          Fenced user information:           
              User name:                     db2fenc1
              GROUP name:                    db2fgrp1
              Home directory:                /home/db2fenc1
                                          
  DB2 Administration server:              
      Instance user information:             
          User name:                         dasusr1
          GROUP name:                        dasadm1
          Home directory:                    /home/dasusr1
                                          
                                          
                                          
  Response file name:                        /root/db2ese.rsp
   
  Checking license agreement acceptance:.......Success
  Command TO be run: "/bin/rpm -ivh '/root/Desktop/DB2/ese/disk1/db2/linux/FILES/gsk7bas-7.0-3.18'.i386.rpm".
  ERROR:Preparing...                ##################################################
   
  ERROR:      package gsk7bas-7.0-3.30 (which IS newer than gsk7bas-7.0-3.18) IS already installed
        package gsk7bas-7.0-3.18 IS already installed
        file /usr/LOCAL/ibm/gsk7/bin/gsk7capicmd FROM install of gsk7bas-7.0-3.18 conflicts WITH file FROM package gsk7bas-7.0-3.30
        file /usr/LOCAL/ibm/gsk7/bin/gsk7cmd FROM install of gsk7bas-7.0-3.18 conflicts WITH file FROM package gsk7bas-7.0-3.30
        file /usr/LOCAL/ibm/gsk7/bin/gsk7ikm FROM install of gsk7bas-7.0-3.18 conflicts WITH file FROM package gsk7bas-7.0-3.30
        file /usr/LOCAL/ibm/gsk7/bin/gsk7ver FROM install of gsk7bas-7.0-3.18 conflicts WITH file FROM package gsk7bas-7.0-3.30
        file /usr/LOCAL/ibm/gsk7/classes/gsk7cls.jar FROM install of gsk7bas-7.0-3.18 conflicts WITH file FROM package gsk7bas-7.0-3.30
        file /usr/LOCAL/ibm/gsk7/classes/ikeycmd.properties FROM install of gsk7bas-7.0-3.18 conflicts WITH file FROM package gsk7bas-7.0-3.30
        file /usr/LOCAL/ibm/gsk7/classes/ikminit.properties FROM install of gsk7bas-7.0-3.18 conflicts WITH file FROM package gsk7bas-7.0-3.30
        file /usr/LOCAL/ibm/gsk7/lib/libgsk7acmeidup.so FROM install of gsk7bas-7.0-3.18 conflicts WITH file FROM package gsk7bas-7.0-3.30
        file /usr/LOCAL/ibm/gsk7/lib/libgsk7cms.so FROM install of gsk7bas-7.0-3.18 conflicts WITH file FROM package gsk7bas-7.0-3.30
        file /usr/LOCAL/ibm/gsk7/lib/libgsk7dbfl.so FROM install of gsk7bas-7.0-3.18 conflicts WITH file FROM package gsk7bas-7.0-3.30
        file /usr/LOCAL/ibm/gsk7/lib/libgsk7drld.so FROM install of gsk7bas-7.0-3.18 conflicts WITH file FROM package gsk7bas-7.0-3.30
        file /usr/LOCAL/ibm/gsk7/lib/libgsk7iccs.so FROM install of gsk7bas-7.0-3.18 conflicts WITH file FROM package gsk7bas-7.0-3.30
        file /usr/LOCAL/ibm/gsk7/lib/libgsk7kicc.so FROM install of gsk7bas-7.0-3.18 conflicts WITH file FROM package gsk7bas-7.0-3.30
        file /usr/LOCAL/ibm/gsk7/lib/libgsk7kjni.so FROM install of gsk7bas-7.0-3.18 conflicts WITH file FROM package gsk7bas-7.0-3.30
        file /usr/LOCAL/ibm/gsk7/lib/libgsk7km.so FROM install of gsk7bas-7.0-3.18 conflicts WITH file FROM package gsk7bas-7.0-3.30
        file /usr/LOCAL/ibm/gsk7/lib/libgsk7krnc.so FROM install of gsk7bas-7.0-3.18 conflicts WITH file FROM package gsk7bas-7.0-3.30
        file /usr/LOCAL/ibm/gsk7/lib/libgsk7krrb.so FROM install of gsk7bas-7.0-3.18 conflicts WITH file FROM package gsk7bas-7.0-3.30
        file /usr/LOCAL/ibm/gsk7/lib/libgsk7krsw.so FROM install of gsk7bas-7.0-3.18 conflicts WITH file FROM package gsk7bas-7.0-3.30
        file /usr/LOCAL/ibm/gsk7/lib/libgsk7msca.so FROM install of gsk7bas-7.0-3.18 conflicts WITH file FROM package gsk7bas-7.0-3.30
        file /usr/LOCAL/ibm/gsk7/lib/libgsk7p11.so FROM install of gsk7bas-7.0-3.18 conflicts WITH file FROM package gsk7bas-7.0-3.30
        file /usr/LOCAL/ibm/gsk7/lib/libgsk7ssl.so FROM install of gsk7bas-7.0-3.18 conflicts WITH file FROM package gsk7bas-7.0-3.30
        file /usr/LOCAL/ibm/gsk7/lib/libgsk7sys.so FROM install of gsk7bas-7.0-3.18 conflicts WITH file FROM package gsk7bas-7.0-3.30
        file /usr/LOCAL/ibm/gsk7/lib/libgsk7valn.so FROM install of gsk7bas-7.0-3.18 conflicts WITH file FROM package gsk7bas-7.0-3.30
   
  WARNING:GSKit installation ON the system failed. RETURN code FROM "/bin/rpm 
  -ivh '/root/Desktop/DB2/ese/disk1/db2/linux/FILES/gsk7bas-7.0-3.18'.i386.rpm" 
  IS "1". Possible causes FOR this failure include:  GSKit IS already installed 
  ON the system,  insufficient space,  image IS corrupted,  OR other system 
  errors.  CHECK FOR possible causes AND run "/bin/rpm -ivh 
  '/root/Desktop/DB2/ese/disk1/db2/linux/FILES/gsk7bas-7.0-3.18'.i386.rpm" again 
  TO install GSKit IF needed.
   
  Command TO be run: "(cd /opt/ibm/db2/V9.1_01; /bin/tar xzvf /root/Desktop/DB2/ese/disk1/db2/linux/FILES/DB2_PRODUCT_MESSAGES_EN_9.1.0.2_linux_i386.tar.gz)".
  Command TO be run: "(cd /opt/ibm/db2/V9.1_01; /bin/tar xzvf /root/Desktop/DB2/ese/disk1/db2/linux/FILES/BASE_CLIENT_9.1.0.2_linux_i386.tar.gz)".
  Command TO be run: "(cd /opt/ibm/db2/V9.1_01; /bin/tar xzvf /root/Desktop/DB2/ese/disk1/db2/linux/FILES/JDK_9.1.0.2_linux_i386.tar.gz)".
  Command TO be run: "(cd /opt/ibm/db2/V9.1_01; /bin/tar xzvf /root/Desktop/DB2/ese/disk1/db2/linux/FILES/DB2_JAVA_HELP_EN_9.1.0.2_linux_i386.tar.gz)".
  Command TO be run: "(cd /opt/ibm/db2/V9.1_01; /bin/tar xzvf /root/Desktop/DB2/ese/disk1/db2/linux/FILES/REPL_QSERVER_9.1.0.2_linux_i386.tar.gz)".
  Command TO be run: "(cd /opt/ibm/db2/V9.1_01; /bin/tar xzvf /root/Desktop/DB2/ese/disk1/db2/linux/FILES/BASE_DB2_SERVER_9.1.0.2_linux_i386.tar.gz)".
  Command TO be run: "(cd /opt/ibm/db2/V9.1_01; /bin/tar xzvf /root/Desktop/DB2/ese/disk1/db2/linux/FILES/JAVA_SUPPORT_9.1.0.2_linux_i386.tar.gz)".
  Command TO be run: "(cd /opt/ibm/db2/V9.1_01; /bin/tar xzvf /root/Desktop/DB2/ese/disk1/db2/linux/FILES/SQL_PROCEDURES_9.1.0.2_linux_i386.tar.gz)".
  Command TO be run: "(cd /opt/ibm/db2/V9.1_01; /bin/tar xzvf /root/Desktop/DB2/ese/disk1/db2/linux/FILES/ICU_SUP_9.1.0.2_linux_i386.tar.gz)".
  Command TO be run: "(cd /opt/ibm/db2/V9.1_01; /bin/tar xzvf /root/Desktop/DB2/ese/disk1/db2/linux/FILES/REPL_SERVER_9.1.0.2_linux_i386.tar.gz)".
  Command TO be run: "(cd /opt/ibm/db2/V9.1_01; /bin/tar xzvf /root/Desktop/DB2/ese/disk1/db2/linux/FILES/JAVA_COMMON_FILES_9.1.0.2_linux_i386.tar.gz)".
  Command TO be run: "(cd /opt/ibm/db2/V9.1_01; /bin/tar xzvf /root/Desktop/DB2/ese/disk1/db2/linux/FILES/BASE_DB2_ENGINE_9.1.0.2_linux_i386.tar.gz)".
  Command TO be run: "(cd /opt/ibm/db2/V9.1_01; /bin/tar xzvf /root/Desktop/DB2/ese/disk1/db2/linux/FILES/DB2_CONTROL_CENTER_HELP_EN_9.1.0.2_linux_i386.tar.gz)".
  Command TO be run: "(cd /opt/ibm/db2/V9.1_01; /bin/tar xzvf /root/Desktop/DB2/ese/disk1/db2/linux/FILES/CONNECT_SUPPORT_9.1.0.2_linux_i386.tar.gz)".
  Command TO be run: "(cd /opt/ibm/db2/V9.1_01; /bin/tar xzvf /root/Desktop/DB2/ese/disk1/db2/linux/FILES/CONFIGURATION_ASSISTANT_9.1.0.2_linux_i386.tar.gz)".
  Command TO be run: "(cd /opt/ibm/db2/V9.1_01; /bin/tar xzvf /root/Desktop/DB2/ese/disk1/db2/linux/FILES/SPATIAL_EXTENDER_CLIENT_SUPPORT_9.1.0.2_linux_i386.tar.gz)".
  Command TO be run: "(cd /opt/ibm/db2/V9.1_01; /bin/tar xzvf /root/Desktop/DB2/ese/disk1/db2/linux/FILES/APPLICATION_DEVELOPMENT_TOOLS_9.1.0.2_linux_i386.tar.gz)".
  Command TO be run: "(cd /opt/ibm/db2/V9.1_01; /bin/tar xzvf /root/Desktop/DB2/ese/disk1/db2/linux/FILES/ADMINISTRATION_SERVER_9.1.0.2_linux_i386.tar.gz)".
  Command TO be run: "(cd /opt/ibm/db2/V9.1_01; /bin/tar xzvf /root/Desktop/DB2/ese/disk1/db2/linux/FILES/COMMUNICATION_SUPPORT_TCPIP_9.1.0.2_linux_i386.tar.gz)".
  Command TO be run: "(cd /opt/ibm/db2/V9.1_01; /bin/tar xzvf /root/Desktop/DB2/ese/disk1/db2/linux/FILES/CONTROL_CENTER_9.1.0.2_linux_i386.tar.gz)".
  Command TO be run: "(cd /opt/ibm/db2/V9.1_01; /bin/tar xzvf /root/Desktop/DB2/ese/disk1/db2/linux/FILES/DATABASE_PARTITIONING_SUPPORT_9.1.0.2_linux_i386.tar.gz)".
  Command TO be run: "(cd /opt/ibm/db2/V9.1_01; /bin/tar xzvf /root/Desktop/DB2/ese/disk1/db2/linux/FILES/REPL_CLIENT_9.1.0.2_linux_i386.tar.gz)".
  Command TO be run: "(cd /opt/ibm/db2/V9.1_01; /bin/tar xzvf /root/Desktop/DB2/ese/disk1/db2/linux/FILES/DB2_DATA_SOURCE_SUPPORT_9.1.0.2_linux_i386.tar.gz)".
  Command TO be run: "(cd /opt/ibm/db2/V9.1_01; /bin/tar xzvf /root/Desktop/DB2/ese/disk1/db2/linux/FILES/LDAP_EXPLOITATION_9.1.0.2_linux_i386.tar.gz)".
  Command TO be run: "(cd /opt/ibm/db2/V9.1_01; /bin/tar xzvf /root/Desktop/DB2/ese/disk1/db2/linux/FILES/INSTANCE_SETUP_SUPPORT_9.1.0.2_linux_i386.tar.gz)".
  Command TO be run: "(cd /opt/ibm/db2/V9.1_01; /bin/tar xzvf /root/Desktop/DB2/ese/disk1/db2/linux/FILES/FIRST_STEPS_9.1.0.2_linux_i386.tar.gz)".
  Command TO be run: "(cd /opt/ibm/db2/V9.1_01; /bin/tar xzvf /root/Desktop/DB2/ese/disk1/db2/linux/FILES/DB2_WEB_TOOLS_9.1.0.2_linux_i386.tar.gz)".
  Command TO be run: "(cd /opt/ibm/db2/V9.1_01; /bin/tar xzvf /root/Desktop/DB2/ese/disk1/db2/linux/FILES/ESE_PRODUCT_SIGNATURE_9.1.0.2_linux_i386.tar.gz)".
  Command TO be run: "(cd /opt/ibm/db2/V9.1_01; /bin/tar xzvf /root/Desktop/DB2/ese/disk1/db2/linux/FILES/XML_EXTENDER_SAMPLES_9.1.0.2_linux_i386.tar.gz)".
  Command TO be run: "(cd /opt/ibm/db2/V9.1_01; /bin/tar xzvf /root/Desktop/DB2/ese/disk1/db2/linux/FILES/DB2_SAMPLE_APPLICATIONS_9.1.0.2_linux_i386.tar.gz)".
  Command TO be run: "(cd /opt/ibm/db2/V9.1_01; /bin/tar xzvf /root/Desktop/DB2/ese/disk1/db2/linux/FILES/DB2_SAMPLE_DATABASE_9.1.0.2_linux_i386.tar.gz)".
  Command TO be run: "(cd /opt/ibm/db2/V9.1_01; /bin/tar xzvf /root/Desktop/DB2/ese/disk1/db2/linux/FILES/SPATIAL_EXTENDER_SAMPLES_9.1.0.2_linux_i386.tar.gz)".
  Installing DB2 file sets:.......Success
  Setting DB2 library path:.......Success
  Executing control tasks:.......Success
  Updating global registry:.......Success
  Starting DB2 Fault Monitor:.......Success
  Updating the db2ls link:.......Success
  Registering DB2 licenses:.......Success
  Setting DEFAULT global profile registry VARIABLES:.......Success
  ERROR:An error occurred during the execution of the command 
  "/opt/ibm/db2/V9.1_01/instance/dascrt  -u dasusr1 -d". The DB2 Administration 
  Server may NOT FUNCTION properly. The RETURN value IS "1".
   
  ERROR:## call function cleanup_reg_list das crt dasusr1
  DBI1103E The Administration Server already EXISTS.  
   
  Explanation: 
   
  The system detects that the Administration Server has already 
  been created ON your system. You can only CREATE one 
  Administration Server ON each system.  
   
  User Response: 
   
  IF you want TO re-CREATE the Administration Server, you have TO 
  DROP the Administration Server first before re-creating it.  
   
   
  DBI1079I Output IS saved IN the log file /tmp/dascrt.log.27843.  
   
  Explanation: 
   
  ALL processed AND failed operations have been saved INTO this log 
  file.  
   
  User Response: 
   
  Do NOT MODIFY this file IN any way. This file IS FOR IBM 
  Technical Support reference.  
   
   
   
  ERROR:One OR more errors occurred while creating the DB2 Administration Server. 
  The DB2 Administration Server may NOT FUNCTION properly. CREATE the DB2 
  Administration Server manually. IF the problem persists contact your technical 
  service representative.
   
  Creating the DB2 Administration Server:.......Failure
  The Fast Connection Manager (FCM) base port was NOT specified FOR the instance 
  "db2inst1". DEFAULT parameters will be used.
   
  The maximum number of logical nodes was NOT specified FOR the instance 
  "db2inst1". DEFAULT parameters will be used.
   
  Initializing instance list:.......Success
  Command TO be run: "cd /opt/ibm/db2/V9.1_01/;/opt/ibm/db2/V9.1_01/instance/db2icrt -a server -s ese -u db2fenc1 db2inst1".
  ERROR:An error occurred while creating the instance "db2inst1". The RETURN code 
  IS "1". CREATE the instance manually USING the command "db2icrt".
   
  ERROR:DBI1765W A non-existing user ID, db2admin, has been detected 
            FROM the registry.  
   
  Explanation: 
   
  The registry IS containing a non-existing user ID. This can be 
  caused BY just removing the instance user ID without first 
  dropping the instance.  This will NOT affect the normal operation 
  of DB2, but it IS recommended TO remove this obsolete user ID 
  FROM the instance list IN the registry.  
   
  User Response: 
   
  TO remove this user ID FROM the registry WITH the command: 
  db2iset -d db2admin 
   
   
  DBI1281E The DATABASE manager configuration file could NOT be 
            initialized.  
   
  Explanation: 
   
  An error occurred when attempting TO initialize the DATABASE 
  manager configuration file. A DB2 instance could NOT be created 
  OR migrated.  
   
  User Response: 
   
  Refer TO the log file FOR problem determination. Resolve the 
  problem AND try the command again. IF the problem persists, 
  please contact IBM Support.  
   
   
  DBI1079I Output IS saved IN the log file /tmp/db2icrt.log.27996.  
   
  Explanation: 
   
  ALL processed AND failed operations have been saved INTO this log 
  file.  
   
  User Response: 
   
  Do NOT MODIFY this file IN any way. This file IS FOR IBM 
  Technical Support reference.  
   
   
   
  ERROR:
  2008-11-10-10.52.35.702626+060 I1G1259            LEVEL: Event
  PID     : 28891                TID  : 3048150720  PROC : db2bp
  INSTANCE: db2inst1             NODE : 000
  FUNCTION: DB2 UDB, RAS/PD component, pdLogInternal, probe:120
  START   : New Diagnostic Log file
  DATA #1 : Build Level, 128 bytes
  Instance "db2inst1" uses "32" bits AND DB2 code release "SQL09012"
  WITH level identifier "01030107".
  Informational tokens are "DB2 v9.1.0.2", "s070210", "MI00183", Fix Pack "2".
  DATA #2 : System Info, 436 bytes
  System: Linux lpcinterldap 6 2 i686
  CPU: total:2 online:2 Cores per socket:2 Threading degree per core:1
  Physical Memory(MB): total:2027 free:51
  Virtual  Memory(MB): total:2539 free:536
  Swap     Memory(MB): total:512 free:485
  Kernel   Params: msgMaxMessageSize:65536 msgMsgMap:65536 msgMaxQueueIDs:16
                   msgNumberOfHeaders:65536 msgMaxQueueSize:65536
                   msgMaxSegmentSize:16 shmMax:4294967295 shmMin:1 shmIDs:4096
                   shmSegments:4096 semMap:32000 semIDs:128 semNum:32000
                   semUndo:32000 semNumPerID:250 semOps:32 semUndoSize:20
                   semMaxVal:32767 semAdjustOnExit:32767
  Information IN this record IS only valid at the time when this file was
  created (see this record's time stamp)
   
  2008-11-10-10.52.35.701151+060 I1261G337          LEVEL: Severe
  PID     : 28891                TID  : 3048150720  PROC : db2bp
  INSTANCE: db2inst1             NODE : 000
  FUNCTION: DB2 UDB, base sys utilities, sqleInitApplicationEnvironment, probe:32
  DATA #1 : Hexdump, 4 bytes
  0xBFD915EC : 60E8 FFFF                                  `...
   
  2008-11-10-10.52.35.706123+060 I1599G319          LEVEL: Severe
  PID     : 28891                TID  : 3048150720  PROC : db2bp
  INSTANCE: db2inst1             NODE : 000
  FUNCTION: DB2 UDB, command line process, clp_bp_main, probe:2
  DATA #1 : Hexdump, 4 bytes
  0xBFD91644 : 60E8 FFFF                                  `...
   
  2008-11-10-10.53.35.686528+060 I1919G375          LEVEL: Error
  PID     : 28889                TID  : 14616256    PROC : db2
  INSTANCE: db2inst1             NODE : 000
  FUNCTION: DB2 UDB, command line process, clp_start_bp, probe:3
  MESSAGE : CLP frontend unable to get REQUEST queue handle
  DATA #1 : Hexdump, 4 bytes
  0xBFC35EAC : 4200 0F87                                  B...
   
  ERROR:An error occurred while configuring the instance "db2inst1".
   
  Configuring DB2 instances:.......Failure
  ERROR:An error occurred while updating the configuration parameter 
  "DASADM_GROUP" to "dasadm1" for the DB2 Administration Server. The return value 
  is "-8050".
   
  ERROR:An error occurred while updating the DB2 Administration Server's 
  configuration WITH the specified administration GROUP. Ensure the DASADM_GROUP 
  setting IS correct BY USING the GET ADMIN CONFIGURATION command. TO MODIFY the 
  value of any DB2 Administration Server configuration parameter, USE the UPDATE 
  ADMIN CONFIGURATION command.
   
  Configuring the DB2 Administration Server:.......Failure
  Updating global profile registry:.......Success
  WARNING:A minor error occurred while installing "DB2 Enterprise Server Edition" 
  ON this computer. Some features may NOT FUNCTION correctly.

[/FONT]
Donc dans le log ci-dessus, je vois qu'il me dit que le compte administrateur a déjà été crée par qui? je ne sais pas mais bon j'ai donc voulu le supprimer par la commande :
/instance/dasdrop et j'ai les réponses suivantes :
SQL4410W The administration server is not active
DBI1070I Program dasdrop completed succesfully
Puis je tente de recréer par la commande :
/instance/dascrt -u db2admin et j'ai les réponses suivantes :
SQL4401C The Administration Server encountered an error during startup
DBI1070I Program dascrt completed successfully

Donc je ne vois pas trop ce que je dois faire, pourriez vous m'eclairer svp.
Merci d'avance