Oracle Analytics Cloud and Server

Products Banner

Question about importarchive.sh command line option "noconnectionparams"

Received Response
132
Views
10
Comments


Hi folks, OAS 6.4 on Linux,

I don't actually use OAS, I do the upgrades, patches, catalog imports etc. Whenever I do a catalog import (Prod -> Test for example), the guy who uses the Windows admin tool says that his connections are gone from there. I thought maybe the "noconnectionparams" option would retain them, but it didn't. I guess I have two questions

1) Is there a way to retain those connections?

2) Is there a good source of documentation for the command line parameters of "importarchive.sh" other than "-help"?

Thanks very much!

Adam

Tagged:

Answers

  • Hi @Adam vonNieda

    As per your question, you have used the option "noconnectionparams : Do not import connection parameters"

    correct?

    How To Run Runcat.sh command without Any Interactive Prompts? (Doc ID 2931865.1)

    If you have backup, yes you can able to restore the same.

    I suggest to use the GUI option --> snapshot Instead of Command-line mode.

    Regards,

    Arjun

  • Thanks for your reply. Yes, I've used the "noconnectionparams " parameter, which I hoped would retain the connection details in the Windows administration tool, but it did not.

    My question is how to do the catalog import but NOT overwrite the connection details, which need to be rebuilt, in the Windows administration tool.

    The reason I'm using "importarchive.sh" rather than the GUI is because this is an automated process.

    Thanks!

    Adam

  • So is your rpd connection pool referencing an external connection(as in connection defined in console >connections)? Is this connection name the same between source and target snapshots?

  • Sumanth V -Oracle
    Sumanth V -Oracle ✭✭✭✭✭

    Hi @Adam vonNieda,

    Please use [encryptionpassword=<encryption password for connections>] parameter when exporting the BAR from source environment.

    Usage: [DOMAIN_HOME]/bitools/bin/exportarchive.sh ssi <Bar file name>.bar encryptionpassword=<password>

    Then use the same when running importarchive in target environment.

    Usage: /importarchive.sh ssi <bar file path> encryptionpassword=<password>

    This should bring in the connection details in RPD as it is in source environment from where BAR file was exported.

  • user5873570
    edited February 7

    Hi,

    I work with Adam and maintain the repository and reports. We maintain connections in the repository as shown below, we don't use the console to maintain connections.

    After the clone, the connection information, user, and password need to be re-entered. They are all blank.

    The connection names are the same in production and non-production. the usernames and passwords are the same as well. really the only difference is the hostname / port / sid of the connection.

    See attached example of the connection.


  • Adam vonNieda
    Adam vonNieda ✭✭
    edited February 7

    So having said the above, back to the original questions

    1) Is there a way to retain those connections (not bring them from the source)?

    2) Is there a good source of documentation for the command line parameters of "importarchive.sh" other than "-help"?

    Thanks!

    Adam

  • Sumanth V -Oracle
    Sumanth V -Oracle ✭✭✭✭✭

    Hi @Adam vonNieda,

    Once the BAR file is imported it overwrites the RPD with the source RPD. We can either import the BAR using "nodatamodel" option to avoid overwriting of the current RPD or simply use uploadrpd command to upload the RPD post import of BAR is successful.

  • Thanks for the replies folks, I'm assuming at this point the answers to both my questions is "no".

  • You can use Externalize connection and define this connection in DV instead of populating the connection pool dsn/credentials values in RPD. As long as source and target use the same connection name, you will not have to do any re-work on the rpd.