Table of Contents

Search

  1. Preface
  2. Using Metadata Manager
  3. Configuring Metadata Manager
  4. Application Resources
  5. Business Glossary Resources
  6. Business Intelligence Resources
  7. Custom Resources
  8. Data Integration Resources
  9. Data Modeling Resources
  10. Database Management Resources
  11. Universal Resources
  12. Managing Resources
  13. Loading and Monitoring Resources
  14. Managing Permissions
  15. Resource Migration
  16. Repository Migration
  17. Appendix A: Metadata Manager Login
  18. Appendix B: Metadata Manager Properties Files
  19. Appendix C: Resource Configuration Files
  20. Appendix D: Glossary

Metadata Manager Administrator Guide

Metadata Manager Administrator Guide

Step 2. Configure sqlnet.ora and tnsnames.ora

Step 2. Configure sqlnet.ora and tnsnames.ora

You must configure the sqlnet.ora and tnsnames.ora files on the Oracle client machines so that Metadata Manager can access the Oracle database.
In the sqlnet.ora file, configure the following parameters:
  • SQLNET.AUTHENTICATION_SERVICES
  • NAMES.DIRECTORY_PATH
  • SQLNET.EXPIRE_TIME
  • SQLNET.ENCRYPTION_TYPES_SERVER
  • SQLNET.ENCRYPTION_SERVER
  • SQLNET.CRYPTO_CHECKSUM_SERVER
  • SQLNET.CRYPTO_CHECKSUM_TYPES_SERVER
  • SQLNET.CRYPTO_SEED
For example, the following code shows possible sqlnet.ora settings when the encryption type is aes256:
SQLNET.AUTHENTICATION_SERVICES = (NTS) NAMES.DIRECTORY_PATH = (tnsnames, ezconnect) SQLNET.EXPIRE_TIME = 0 SQLNET.ENCRYPTION_TYPES_SERVER = (aes256) SQLNET.ENCRYPTION_SERVER = required SQLNET.CRYPTO_CHECKSUM_SERVER = required SQLNET.CRYPTO_CHECKSUM_TYPES_SERVER = (md5) SQLNET.CRYPTO_SEED = "abcd1234"
In the tsnames.ora file, add an entry for the Oracle server that uses ASO.

0 COMMENTS

We’d like to hear from you!