Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Data Archive 6.4.4
  • All Products

Table of Contents

Search

  1. Preface
  2. Starting Data Archive
  3. System Configuration
  4. Database Users and Privileges
  5. Source Connections
  6. Target Connections
  7. Archive Store Configuration
  8. Datatype Mapping
  9. Database Optimization
  10. SAP Application Retirement
  11. z/OS Source Data Retirement
  12. Seamless Data Access
  13. Data Discovery Portal
  14. Security
  15. SSL Communication with Data Vault
  16. LDAP User Authentication
  17. Auditing
  18. Running Jobs from External Applications
  19. Salesforce Archiving Administrator Tasks
  20. Upgrading Oracle History Data
  21. Upgrading PeopleSoft History Data
  22. Data Archive Maintenance
  23. Storage Classifications
  24. Appendix A: Datetime and Numeric Formatting
  25. Appendix B: Data Archive Connectivity

Administrator Guide

Administrator Guide

Back Next

Netezza Source Connections

Netezza Source Connections

Define archive source connection properties to connect to applications on Netezza databases.
A Netezza adapter is available for both Data Archive and the Enterprise Data Manager. When you configure a Netezza connection you must use the Netezza adapter.
Netezza connections do not require specific privileges for database users. Netezza databases have only one database user that is granted all required privileges.
When you create a Netezza source connection, the user name and password for the administration, application, and staging users are identical. When you create a source or target connection, you must select the check box
Parallel Entity Run
 and deselect the check box
Use Staging
.
To create an entity on a Netezza source, you must enter a value for all default interim columns in the Enterprise Data Manager. The
Select Clause
 field cannot be empty, unlike Oracle.
You can configure the following source connection properties:
Host
IP address of the source application database server.
Port
Port of the source application database server.
Service Name
Database name for the source application database server.
ILM Repository Administrator User
Default administration database user for the source database server. Used to connect to the source database. You can provide any user name, such as database connection user or a read-only user.
Admin Login Name
Login name for the administration database user.
Password
Password for the administration login name.
Application User Name
Database user that owns the application tables that you want archive. The application user name is identical to the administration user name.
Application Login Name
Login name that connects to the source database that contains the data you want to archive. Only used for the database connection.
The application login name is identical to the administration login name.
Password
Password for the application login name.
The password is identical to the administration login password.
Staging User Name
Staging database user for the source database. The staging user name is identical to the administration user name.
The staging database user stores interim tables for business rule validation and generates candidates during the archive process. The staging user typically resides in the source database.
Staging Login Name
Login name for the staging database.
The staging login name is identical to the administration login name.
Password
Password for the staging login name.
The password is identical to the administration login password.
Staging Tablespace
Not applicable. You can enter any value in this field.
Index Tablespace
Not applicable. You can enter any value in this field.
Use Staging
You must clear this check box.
JDBC Fetch Size
Controls the number of rows that the system fetches in one batch from one table if you use JDBC to connect to the source database.
Only change the default value if you receive an out-of-memory error when the archive job copies data to the destination. You may get the out-of-memory error if the source table has large objects in each row, such as CLOBS or BLOBS data types. If you receive this error, then reduce the fetch size.
Default is 1000.
Database Link to Production (Restore Only)
Database link name that connects the history database to the production database. This attribute is required scenarios, the history database is the source, and the production database is the target.
Enter "NONE" in this field because Netezza does not create dblinks.
Use Staging User for Deletes
Not applicable.
Default is disabled.
Target Attachment Location
Target location for external attachments. Enter the location where you want to archive the external attachments to. You must have write access to the directory.
This attribute only applies to external attachments.
Source/Staging Attachment Location
Required to restore archived attachments from the history database or from the Data Vault to the source database. The definition depends on the archived attachment location and whether the attachments are encrypted.
To restore attachments from the history database and non-encrypted attachments from the Data Vault, enter the current location of the archived attachments. This is the location where you originally archived the attachments to. You must have read access to the directory.
To restore encrypted attachments, such as Siebel attachments, from the Data Vault, enter a temporary location that is accessible to the ILM engine and the Data Vault Service for External Attachments component. The restore job moves the attachments from the Data Vault Service AM_ATTACHMENTS table to this temporary location.
Staging Script Location
Required to restore archived attachments from the history database or from the Data Vault to the source database. Enter a temporary location to store the script that the restore job generates.
For attachments in the history database and non-encrypted attachments from the Data Vault, the script moves the attachments from the source attachment location to the target attachment location.
For encrypted attachments in the Data Vault, the script uses the source application encryption utility to encrypt the attachments back into the source application proprietary format. Then, the script moves the attachments from the staging attachment location to the target attachment location.
Move Attachments in Synchronous Mode
Determines whether the archive job automatically archives external attachments or whether you run a standalone job to move the attachments after the archive job completes. If you provide a source file location for attachments, the archive job creates SQL scripts in the file server location and associates the scripts with the archive job ID.
If enabled, the archive job runs the scripts during the archive process. The run procedures configuration in the entity determines when the archive job archives the attachments.
If disabled, you must initiate the movement after the archive job completes. You can manually run the scripts in the file server location or you can run a standalone job to move the attachments. If you run the standalone job, you must provide the archive job ID. The job then looks for the scripts that are associated to the archive job ID.
This attribute only applies to external attachments.
Parallel Entity Run
Determines the interim table names in the entity if you want to run the entity in parallel archive jobs. For example, you may extract data in parallel from two different organizations in the same human resource entity. The system creates interim tables in the staging database user. However, the tables need to be differentiated so the archive jobs know which interim tables are relevant for that job.
By default, the system creates interim table names with the same name in EDM. If you enable this attribute, then the system creates the interim table names with the following syntax: 
<table name>_<job ID>
You must enable this check box.
0 COMMENTS
We’d like to hear from you!