2.1 For AIX only
2.1.4 Migrating from IBM Directory Server 4.1 or
2.1.2 Error code -1 at startup
IfDB2 isnotalreadystarted,youmightseethefollowingmessage whenstarting theserver:
Error code -1 from odbc string:" SQLConnect " ldapdb2b.
ThisoccursbecausetheIBMDirectoryServeristryingtoconnecttoDB2,before DB2 isstarted.Ifyouseethemessage:
SQL1063N DB2START processing was successful.
youcanignorethepreviouserrormessagebecausetheDirectoryServer hasstarted DB2 andsubsequentlyconnectedtoit.
2.1.3 Problem with MALLOCTYPE=buckets
Theperformance enhancingMALLOCTYPE=bucketsenvironmentrequires:
v TheAIX5.2operatingsystem MaintenanceLevel03thatcontains afixforAPAR IY50668.
v Theibmslapdcommandmust bestartedina loginsession thathastheulimit fordataandmemorysettounlimited.
# ulimit -d unlimited
# ulimit -m unlimited
2.1.4 Migrating from IBM Directory Server 4.1 or 5.1 with DB2 7.2 on AIX
IfyouaremigratingfromIBMDirectoryServer4.1onAIX, youmust upgrade your DB2versiontoDB2EnterpriseServerEdition8.1, 64-bit.Complete instructions werenotgivenintheInstallationand ConfigurationGuideforthis migration. Therefore,usethefollowinginformationtomigrate fromIBMDirectory Server 4.1or5.1with DB27.2onAIX.
Tomigrate anexistingIBMDirectoryServer4.1or5.1onAIXandmigrateDB2 EnterpriseServer Edition7.2, 32-bit,toDB2EnterpriseServerEdition8.1,64-bit, usethefollowingprocedure:
Pre-installationsteps:
1. Migrate theDB2 instance.Beforeyoucanmigrate aDB2instance,all
applicationsusinganydatabasesownedbytheinstancemust beterminated.
Toprepare aDB2instancefor migration,usethefollowingprocedure:
a. LoginastheDB2 instanceowner.
b. Besure thattherearenoapplicationsusinganydatabasesownedbythis DB2instance.Toget alistofallapplicationsownedbytheinstance,use thedb2listapplicationscommand.Youcanendasession byentering the db2terminatecommand.Donotforceterminationofapplicationsusing thedb2forceapplicationsallcommand,because someapplicationsmight haveunexpectedbehaviorwhentheyare terminatedusingthiscommand.
SeetheDB2Command Referencefordetailedinformationaboutthese commands.
c. Whenallapplicationsarecomplete,stop alldatabaseserverprocesses ownedbytheDB2 instancebyentering thedb2stopcommand.
d. StoptheDB2licensedaemonbyenteringthedb2licdendcommand.
e. Stopallcommandlineprocessor sessionsbyenteringthedb2terminate commandineachsessionthatwasrunningthecommandlineprocessor.
f. Enterthedb2_killcommandto cleanupanyremainingDB2 resources.
g. Logoff.
2. Verifythatthedatabasecanbe migrated.Therearealsomigration
considerations youshouldtakeintoaccountifyouare usingtheVersion2 user exitprogram.
DB2 providesthedb2ckmigmigrationcommand, whichisusedtoverify whether allcatalogeddatabasescanbemigrated.Thedb2imigr command usesthedb2ckmigcommandtoverifywhetherthecatalogeddatabasescanbe migrated.
Toensurethatyoucanmigratetheinstance,runthedb2ckmigcommand. If instance migrationfailed,youmustcorrecttheerrorsreportedbythis
command. Youcanrunthedb2ckmig commandagainto verifythattheerrors havebeen corrected,andthenmigrate theinstance.
For detailedinformationaboutthedb2ckmigcommand, refertotheDB2 Command Reference.
Toverify thatallcatalogeddatabasescanbemigrated,perform thefollowing steps:
a. Loginastheinstance owner.
b. Enterthefollowingcommand:
db2ckmig ldapdb2 -l /home/ldapdb2/mig.log
c. Check thelogfile.Thelogfiledisplaystheerrorsthatoccurwhenyourun thedb2ckmigcommand. Ifitshowsanyerrors,perform correctiveactions.
d. Check thatthemigration logfileisemptybeforecontinuingwiththe instancemigration.
e. Backupthedatabaseaftermaking corrections.
3. Install DB2EnterpriseServer Edition8.1,64-bit.
4. Backupthepreviousversionsof theslapd32.conforibmslapd.confand any schemafilesfromthe/usr/ldap/etcdirectorytoa directorythatisnota subdirectoryof/usr/ldap.
Theseincludefiles withthefollowingfileextensions:
v .oc v .at v .conf
and thefollowingfiles:
v
V3.ldapsyntaxes v V3.matchingrules v
V3.modifiedschema
5. IfyouinstalledwiththeInstallShieldGUI,uninstall usingtheInstallShield GUI.However, donotuninstall DB2.Ifyouinstalledusingnativeutilities,do notuninstallyet.
Youcancheck toseeif youinstalledIBMDirectoryServerwith the InstallShieldGUIbyusingthefollowingprocedure: Lookinthe/usr/ldap directory. Ifyouhavea subdirectorynamed_uninst,youinstalledwiththe InstallShieldGUI,andyoumustuninstall withtheInstallShieldGUI.(Donot usesmittouninstall).Tostarttheinstallation,changedirectoriestothe /usr/ldap/_uninstdirectory, andtype./uninstall,and completethe uninstallation.Thenyoumust manuallyremoveanything leftinthe
/usr/ldap directory.(SeetheIBMDirectoryServer Installationand Configuration Guideforyourrelease.)
6. Migrate theDB2 instance.Onlylocalcatalogeddatabasesthatresideinthe DB2 instancearecheckedformigration.Uncatalogeddatabasesmightbe unusable aftertheinstancehasbeenmigrated.
Afteraninstanceisreadyformigration,usethedb2imigr commandto migrate theinstanceasfollows:
a. Loginasauser withrootauthority.
b. Ifthelibrary_pathenvironmentvariable isset to/usr/liband thereisa linkin/usr/libtotheVersion7libdb2shared library,this cancausean errorwhenusingthedb2imigr command.Tofixtheerror,resetthe
library_pathenvironmentvariable sothatit doesnotreferencethelibraries inthosepaths byentering thefollowingcommand:
unset LIBPATH
c. Runthedb2imigrcommandasfollows:
/usr/opt/db2_08_01/instance/db2imigr [-d] [-a AuthType]
[-u fencedID] InstName
where
v -dsetsthedebugmodethatyoucanusefor problemdetermination.
Thisparameterisoptional.
v -aAuthTypespecifiestheauthentication typefortheinstance.Valid authenticationtypesare(SERVER),(CLIENT),and(DCS).Ifthe-a parameterisnotspecified,theauthenticationtype defaultsto(SERVER), ifaDB2serverisinstalled.Otherwise,theAuthTypeissetto(CLIENT).
Thisparameterisoptional.
Notes:
1) Theauthentication typeoftheinstanceappliestoalldatabases ownedbytheinstance.
2) Whileauthenticationtype(DCE) isan optionalparameter,it isnot validtochoose(DCE)forthis command
v -ufencedIDistheuser underwhichthefenceduser-definedfunctions (UDFs)and storedprocedureswillrun.Thisparameter isoptionalonly whenaDB2Run-TimeClientisinstalled.Itisrequiredfor allotherDB2 products.
v InstNameistheloginnameoftheinstanceowner.
7. ConverttheDB2instance toa64-bit width,usingthefollowingprocedure:
a. Loginasauser withrootauthority.
b. Runthedb2iupdtcommandasfollows:
/usr/opt/db2_08_01/instance/db2iupdt -w 64 InstName
c. AftermigratingtheDB2instance,reset LIBPATHtoitsoriginalsetting 8. Migrate thedatabase ownedbytheinstance,usingthefollowingsteps:
a. Logonwitha userIDthathasSYSADMauthority,suchastheinstance owner.
b. Ensurethatthedatabaseyouwanttomigrate iscataloged.
c. Whileloggedonastheinstanceowner,typedb2start.
d. Typedb2.
e. AttheDB2 commandprompt,typethefollowing:
migrate database DATABASE-NAME
9. Initialize thedatabase managerconfigurationparameterUTIL_IMPACT_LIM to itsdefaultvalue.TheUTIL_IMPACT_LIMconfigurationparameterdidnot exist forUDB7.1andonmigration toEnterpriseServer Edition8.1itis assigneda valueof0. Thevalidrangeforthisparameter is1 to100.Usethe followingprocedure:
a. Logonwitha userIDthathasSYSADMauthority.
b. Rundb2.
c. AttheDB2commandprompt,typethefollowing:
update database manager configuration using UTIL_IMPACT_LIM value
value shouldbekeptlow:between1and 10.
10. If youinstalledusingoperatingsystemutilities,uninstallIBM Directory Server 4.1or5.1,usingoperatingsystemutilities.
Youcancheck toseeif youinstalledIBMDirectoryServerwith operating system utilitiesbyusingthefollowingprocedure: Lookinthe/usr/ldap directory. Ifyouhavea subdirectorynamed_uninst,youinstalledwiththe InstallShieldGUI,andyoumustuninstall withtheInstallShieldGUI.(Donot usesmittouninstallinthiscase). Ifyoudo nothaveasubdirectorynamed _uninst, youinstalledusingoperatingsystemutilities,and youmust uninstall usingoperatingsystemutilities. (SeetheIBMDirectoryServerInstallationand ConfigurationGuideforyourreleasefor instructions.)
Installationsteps:
11. Install IBMTivoliDirectoryServer5.2usingtheInstallShieldGUIorSMIT.
(See theInstallationand ConfigurationGuideforinstructions.) Post-installation steps:
12. Migrate theconfigurationand schemabyexecutingthemigrate52 script.Type thefollowingcommandsata commandprompt:
cd installpath/etc
../sbin/migrate52 -s backuppath
where backuppathisthepathwhereyoubacked upthefilesin step4onpage 22.
Note: Youmustrunthemigrate52 scriptevenif youdidnotmodifythe previousschema.Therearenew schemafiles andentriesinthe ibmslapd.conffilethatarenotcompatiblewithpreviousversions.
13. Try tostarttheserverbytypingibmslapd.Iftheservercomesupin configurationonlymode,dothefollowing:
a. Unconfigure thedatabase withoutdestroyingit.(Thedatabaseinstance anddatabase arekept,buttheibmslapd.conffileisupdated.)Use the ldapucfg -dcommand: For example:
# ldapucfg -d
You have opted to unconfigure the existing database ’ldapdb2’.
Do you want to....
(1) Leave this database on your system (just unconfigures), or (2) Completely erase the database (and any data in it)?: 1
You have chosen the following actions:
Database ’ldapdb2’ in instance ’ldapdb2’ will be unconfigured.
Database ’ldapdb2’ will be left on your system.
Instance ’ldapdb2’ will be left on your system.
Do you want to....
(1) Continue with the above actions, or (2) Exit without making any changes: 1
Unconfiguring IBM Tivoli Directory Server Database.
Removing local loop back from database: ’ldapdb2’.
Removed local loop back from database: ’ldapdb2’.
Unconfiguring database: ’ldapdb2’
Unconfigured database: ’ldapdb2’
Starting database manager for instance: ’ldapdb2’.
Started database manager for instance: ’ldapdb2’.
Unconfigured IBM Tivoli Directory Server Database.
IBM Tivoli Directory Server Unconfiguration complete.
b. Configuretheexistingdatabaseinstanceand database,andupdatethe ibmslapd.conf file,usingthefollowingcommand:
ldapcfg -l /home/ldapdb2 -a ldapdb2 -w <password> -d ldapdb2 -t ldapdb2
For example:
# ldapcfg -l /home/ldapdb2 -a ldapdb2 -w ldaptest -d ldapdb2 -t ldapdb2 -n
You have chosen the following actions:
Database ’ldapdb2’ will be configured in instance ’ldapdb2’.
Configuring IBM Tivoli Directory Server Database.
Cataloging instance node: ’ldapdb2’.
Cataloged instance node: ’ldapdb2’.
Starting database manager for instance: ’ldapdb2’.
Started database manager for instance: ’ldapdb2’.
Updating the database: ’ldapdb2’
Updated the database: ’ldapdb2’
Updating the database manager: ’ldapdb2’
Updated the database manager: ’ldapdb2’
Enabling multi-page file allocation: ’ldapdb2’
Enabled multi-page file allocation: ’ldapdb2’
Configuring database: ’ldapdb2’
Configured database: ’ldapdb2’
Adding local loop back to database: ’ldapdb2’.
Added local loop back to database: ’ldapdb2’.
Stopping database manager for instance: ’ldapdb2’.
Stopped database manager for instance: ’ldapdb2’.
Starting database manager for instance: ’ldapdb2’.
Started database manager for instance: ’ldapdb2’.
Configured IBM Tivoli Directory Server Database.
IBM Tivoli Directory Server Configuration complete.
14. If youarenotusingDB27.2foranythingotherthanIBMDirectoryServer, uninstall it.