This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Specific links you will want to bookmark for future use
RESTORE fails with SQL30082N RC=3 if an LDAP database with the same name already exists in Active Directory(RIMS)
Restore fails with 'SQL30082N Security processing failed with reason '3' ('PASSWORD MISSING')' when there's still a database with the same name in the Windows Active Directory but on another server.The restore completes when the other db is uncatalogged before, 'db2 uncatalog ldap db xyz'.Database 5 entry: Database alias = adonis3 Database name = ADONIS3 Node name = TA0SAT01Database release level = d.00 Comment = Directory entry type= LDAP Catalog database partition number = -1 Gateway node name = Alternate server node name = Atlernate server gateway node name = D:\DB2Backup>db2 restore db adonis3 from d:\DB2BackupSQL30082N Security processing failed with reason '3' ('PASSWORD MISSING'). D:\DB2Backup>db2 uncatalog ldap db adonis3 DB20000I The UNCATALOG LDAP DATABASE command completed successfully.D:\DB2Backup>db2 restore db adonis3 from d:\DB2Backup DB20000I The RESTORE DATABASE command completed successfully. This design is not consistent compared to the creation of a database. It is possible to create a database with the same name on Server 2 nevertheless a LDAP database entry exists already on Server 1. Following circumvention is currently required to get the wanted database restored: Server 1: db2 uncatalog ldap db xyz Server 2: db2 restore db xyz from d:\ Server 2: db2 uncatalog ldap db xyz Server 1: db2 catalog ldap db xyz At restore we should check if the alias database name is 'Directory entry type = LDAP' . If so we should just restore but not implicit connect to the LDAP database on another server..
Do not place IBM confidential, company confidential, or personal information into any field.