Skip to main content

Additional Features

Time Out Option

Hubble applications do not have a time out option, but the database server can usually be configured to drop connections after a period of inactivity. Hubble will then offer to reconnect, however it does not demand a user password when doing so.

Journals and Journal Receivers

Background

Journaling is an AS/400 integrated database feature which keeps track of changes made to physical files (e.g. record created, deletion, modification; file open and close). this information can be used for audit purposes or to undo/redo changes made.

Any journal receiver which is out of use can be deleted manually immediately or automatically by the system. For detailed information on the subject of Journal Management beyond what is provided below, please refer to IBM’s website:

http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_71/rzaki/rzakiconcepts.htm

Usage in Hubble

Hubble uses journals and their associated journal receivers for transaction support when updating the Object Repository tables.

Journal and journal receiver creation happens automatically when creating a SQL collection. When executing 'CREATE COLLECTION' via STRSQL, among other objects the system creates QSQJRN (the journal) and QSQJRN0001 (the journal receiver). The journal provides a hook into the physical file activity. In order to record activity, the journal uses a journal receiver which is created using CRTJRNRCV. Conceptually, the journal can be seen as a notebook and the receiver as a page within it. Like a page in a notebook, a receiver can become filled up; when this is the case, the journal can be configured to log a message and have an administrator create a new receiver and attach it, or the system can just create a new receiver automatically using the full one as a template

Deleting Journals

If journaling is used for auditing purposes, then the administrator would back up detached (full) receivers to tape and then delete them. In case the journals are only used to support transactions (as is the case with the object repository), the detached receivers can simply be deleted.

To turn on automatic receiver deletion, run the following command (assuming that the collection is called HUBBLE): CHGJRN JRN(OSTORE/QSQJRN) DLTRCV(*YES). This will only delete the journal receivers for the HUBBLE library.

You can remove the existing Journal Receivers that are not being used. This is done by the library so it won’t affect other processes or jobs outside of those in the Hubble library. The system will not allow you to remove Journal Receivers that are being used currently.

Remove DWTEMP Files

On Oracle databases, there are times when the DWTEMP tables are not deleted from the database. This can happen whenever Hubble is closed before an inquiry is closed with the Close Inquiry button or if the software experiences a database time out.

Oracle database administrators can use the following unsupported example to create a script that will clean out DWTEMP tables that are at least 1 day old. Please provide the below script to your database administrator for their review to confirm the script meets your company policies and needs.

DECLARE

sqlstmt    VARCHAR2(255);

CURSOR    dropcursor IS

SELECT 'DROP TABLE ' || owner || '.' || object_name || ' CASCADE CONSTRAINTS'

FROM all_objects

WHERE object_name LIKE 'DWTEMP%' AND object_type = 'TABLE' AND created < SYSDATE - 1;

BEGIN

OPEN dropcursor;

FETCH dropcursor INTO sqlstmt; LOOP

EXIT WHEN dropcursor%NOTFOUND; EXECUTE IMMEDIATE sqlstmt;

--    dbms_output.put_line ( sqlstmt );

FETCH dropcursor INTO sqlstmt; END LOOP;

CLOSE dropcursor; EXCEPTION

WHEN OTHERS THEN

dbms_output.put_line ( 'SQL error while executing ' || sqlstmt || ' / SQL Error ; ' || SQLERRM);

END;

/

Unable to Log in: Possible Reasons

There are a number of possible reasons as to why you may not be able to log in to the application. Be sure to check the following items:

  • Ensure that the username and password are entered correctly.
  • If the connection is to a JD Edwards World configuration, the username and password will be the user’s normal JD Edwards username and password.
  • If the connection is to a JD Edwards EnterpriseOne configuration, the username will be their normal JD Edwards username and their password is that which is set in Administrator in the user’s profile.
  • If the connection is to EBS, the username is their normal EBS username and their password is that which is set in Administrator in the user’s profile.
  • Check that the username exists in the Hubble Object Repository and that the user has Read permissions to the Data Source Connection and Profile being used.

Error that my user is not defined in the F0093 library - This error is saying that your user group or role is not associated with this environment it is associated with in the JD Edwards F0093 table.

The specific error is: User '<username>' is not defined in the [<database>].[<table_prefix>].[F0093] library.

A Hubble Administrator can confirm this by using the following SQL to see if the user exists.

SELECT LLUSER,LLLL

FROM<TABLE_PREFIX>.F0093

WHERE LLLL = '<ENVIRONMENT>'

AND LLUSER IN ('<USERNAME>','<USERSGROUPOR_ROLE>')

Where:

  • <TABLE_PREFIX> is the table prefix
  • <ENVIRONMENT> is the environment
  • <USERNAME> is the JD Edwards username
  • <USERSGROUPOR_ROLE> is the user’s group or role

If the user has access to that environment, at least one row will be returned. If the user does not have access to that environment, no results will be returned.

For this example we will be using database OPENWORLD2007, table prefix DBO, environment DEMO900, user JASON and groups/roles SUPPORT and SUPPORT1.

USE OPENWORLD2007

SELECT LLUSER,LLLL

FROMDBO.F0093

WHERE LLLL = 'DEMO900'

AND LLUSER IN ('JASON','SUPPORT','SUPPORT1')

Running the SQL against the database returns zero rows.

Selecting all columns and returning all results reveals that groups/roles SUPPORT and SUPPORT1 only have access to environment DEMO810NT.

To resolve this issue, the user or user’s group/role will need to be granted access to the environment from within JD Edwards.

In Administrator, view the profile being used to log into the Hubble application to verify which JD Edwards environment your user ID is being validated against. To do this, follow these steps:

  1. Log into the repository if you are not logged in already.
  2. Expand the Data Sources node in the left panel.
  3. Select Profiles and in the right panel.
  4. Right-click on the specific profile being used to log into the application.
  5. Select Edit.
  6. Click Next in the Profile Wizard until you get to the Environment and Model Business Unit screen.
  7. The environment defined here is that which is being used in JD Edwards to validate the user signing in: