Application Pack 8.1.3.3.0 FAQs

  1. The the cx_Oracle connection is failing in DS with the following error in OEL 8.

    Fail to execute line 4: cx_Oracle.connect(dsn=dsn_alias)\nTraceback (most recent call last):\n File "/tmp/1638454321889-0/zeppelin_python.py", line 163, in <module>\n exec(code, _zcUserQueryNameSpace)\n File "<stdin>", line 4, in <module>\ncx_Oracle.DatabaseError: DPI-1047: Cannot locate a 64-bit Oracle Client library: "libnsl.so.1: cannot open shared object file: No such file or directory". Install the libnsl package as below: yum install libnsl or sudo yum install libnsl

  2. Python Interpreter fails with the `py4j` Error

    When running interpreters locally, they assume all the dependencies to be already installed and available. Python Interpreter needs `py4j` Package, exact steps to install it depend on the Operating System. If you use `pip`, it can be done with ```bash pip install --user py4j ``` Install the package for all users, root user can run this command without `--user`.

  3. What is the reason for the http error code 401 when I successfully log in to the MMG Application while MMG Studio is down?

    If MMG Studio is not up during the MMG application login, the mmg-ui logs capture the http error code : 401 . Since the cookie creation is done during MMG application login, the user must re login to the MMG application once the Studio is up and running.

  4. What should I do when the following error message is displayed, and the SSL module is unavailable for Linux 8?

    urllib3.exceptions.SSLError: Can’t connect to HTTPS URL because the SSL module is not available. During handling of the above expectation, another exception occurred:

    1. Install the compat-openssl10 module on Linux 8.
    2. Log in to the server as a root user where MMG Application is installed.
    3. Run the following Shell command: yum -y install compat-openssl10.
  5. Why do multiple commits/versions appear in my remote Git repository after my first push, even though I only pushed once?

    When you push a local git repository to a remote one for the first time, all the commits that exist in your local repository’s history for the branch that is being pushed are transferred to the remote repository. This happens even if the remote is new or empty. This is standard git behavior. If your local repository was initialized earlier, or was linked to a different remote connection, then all its' commits will still remain in your local git history. When you add a new remote connection and perform a push action, git pushes the entire commit history, not just the most recent change. So the remote connection will reflect all your local commits.

    Key Points:
    • Git tracks the full commit history locally, regardless of remote connections.
    • Pushing to a new remote connection brings the entire history of your pushed branch.
    • If you want only specific commits in the new remote connection, you must create a new repository or filter your history before pushing.