ADD A NEW IDEA

All ideas

Showing 14954

Synchronize HISTORY file with the TSM server object list.(RIMS)

Since the objects on the TSM server are expired remotely, DB2 is not aware of this because the local HISTORY file does not sync with TSM. What we are requesting is a method to synchronize DB2's HISTORY file with the TSM server object list. This wi...
over 9 years ago in Db2 / Backup/Restore/ Rollforward/ Recover 0 Not under consideration

BACKUP/RESTORE should provide support for external objects.(RIMS)

when customer archives backup images (they have to keep 7 years worth of trade data), they must manually archive non-data objects (such as function/procedure definitions, libraries, and other things required for the database to run properly). � ...
over 9 years ago in Db2 / High Availability and/or Disaster Recovery 0 Not under consideration

Ability to backup/clone a database across the network (redirected restore)(RIMS)

Verizon needs the capability to issue a set write suspend IO command on database. Get the data to another instance at another location and bring it up. Informix has this ability and Verizon likes it. This is called a redirected restore. Verizon's ...
over 9 years ago in Db2 / High Availability and/or Disaster Recovery 1 Not under consideration

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 uncata...
over 9 years ago in Db2 / High Availability and/or Disaster Recovery 0 Not under consideration

Optimizer documentation needs enhancement(RIMS)

Optimizer documentation needs enhancement. Until a lab services consultant came onsite to help them they were not able to adequately tune their queries due to poor optimizer documentation. Benefit: Verizon is now a very big user of DB2 and we spen...
over 9 years ago in Db2 / Analytical Functions 0 Not under consideration

LOCK ESCALATION: Ability to specify table-level lock-escalation criteria.(RIMS)

Customer wants more granularity on lock-escalation semantics. currently, lock escalation occurs either when an application hit's the MAXLOCKS constraint, or when the database LOCKLIST becomes full. Since lock-escalation is more detrimental on tabl...
over 9 years ago in Db2 / Serviceability 0 Not under consideration

Allow a DBA connection even if maximum connections has been exceeded.(RIMS)

Note from customer: Jill, We need a feature enhancement, where there is a way for a DBA to always be able to connect to the DB (at least one connection), even if maxappls, maxagents, maxwhatever has been hit. DBAs shouldnt have to force off appli...
over 9 years ago in Db2 / Serviceability 0 Not under consideration

BACKUP/RESTORE should support parallelcompression of backupstripes when using native compress option(RIMS)

Headline Cont...(thisiscurrentlysingle-threadpertablespace).Description -currently, Backup will fetch from multiple tablespaces using multiple concurrent prefetcher sub-agents. However when Backup Compression is enabled, data is forced through Bac...
over 9 years ago in Db2 / High Availability and/or Disaster Recovery 0 Not under consideration

Improve Installation Documenation

Windows OS 'Installation Instructions' need to be updated to account for the current complexity of security/privileges environments. Specifically, where an end-user account is not a member of the 'most-privileged' (i.e. Administrator) group accoun...
over 9 years ago in SPSS Statistics 0 Not under consideration

Track total CPU time, total Memory Usage of LSF Job Process IDS

Request LSF process accounting to do something like: only show the LSF admins the top-most consumer of CPU time, and report only on that.
over 9 years ago in Spectrum LSF 2 Not under consideration

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.