JDE SSO with Azure AD with MFA

 

JDE SSO with Azure AD with MFA

SQL Server - Find Duplicate Submitted Jobs JDE

Find Duplicate Submitted Jobs JDE

WITH CTE(JCEXEHOST,JCFNDFUF2, duplicatecount)

AS (SELECT JCEXEHOST,JCFNDFUF2, ROW_NUMBER() OVER(PARTITION BY JCEXEHOST,JCFNDFUF2 ORDER BY  JCEXEHOST,JCFNDFUF2) AS DuplicateCount

    FROM SVM920.F986110 WHERE JCJOBSTS IN ('W') AND JCORGHOST='Enterprise_Server')

SELECT * FROM CTE WHERE DuplicateCount > 1;

Delete Duplicate Submitted Jobs JDE

WITH CTE(JCEXEHOST,JCFNDFUF2, duplicatecount)

AS (SELECT JCEXEHOST,JCFNDFUF2, ROW_NUMBER() OVER(PARTITION BY JCEXEHOST,JCFNDFUF2 ORDER BY  JCEXEHOST,JCFNDFUF2) AS DuplicateCount

    FROM SVM920.F986110 WHERE JCJOBSTS IN ('W') AND JCORGHOST='Enterprise_Server')

DELETE FROM CTE WHERE DuplicateCount > 1;

JDE Workflow Table

 

JDE Workflow Table

E1: WRKFLW: Frequently Asked Questions on EnterpriseOne Workflow (Doc ID 1329683.1)

F98800      Process Master

F98800D    Process Master Alternate Description
F98800T    Process Master Supplemental Information
F98810      Task Master
F98810D    Task Master Alternate Description
F98811      Task Specifications
F98830      Process Task Associations
F98840      Organizational Structure Master
F98845      Organizational Structure Rule

For 8.9 and beyond:
F98820      Workflow Engine
F98850      Argument Mapping
F98870      Process Observer

READ BLOB in SQL Server

 

SELECT vrpid, vrvers, CAST ( CAST ( vrpodata AS VARBINARY(MAX)) AS NVARCHAR(MAX)) [POVal], vrvcd as DateChanged from pd920.f983051

where (vrpid like 'P%' or vrpid like 'R%')

and vrvcd > 12360

order by vrvcd DESC;

 

SELECT vrpid, vrvers, CAST ( CAST ( vrpodata AS VARBINARY(MAX)) AS NVARCHAR(MAX)) [POVal] from pd920.f983051

where (vrpid like 'P%' or vrpid like 'R%') and CAST ( CAST ( vrpodata AS VARBINARY(MAX)) AS NVARCHAR(MAX)) like '%:\%' or CAST ( CAST ( vrpodata AS VARBINARY(MAX)) AS NVARCHAR(MAX)) like '%\\%'

order by vrpid;

 

SELECT vrpid, vrvers, CAST ( CAST ( vrpodata AS VARBINARY(MAX)) AS NVARCHAR(MAX)) [POVal] from pd920.f983051

where (vrpid like 'P%' or vrpid like 'R%') and CAST ( CAST ( vrpodata AS VARBINARY(MAX)) AS NVARCHAR(MAX)) like '%:\%' or CAST ( CAST ( vrpodata AS VARBINARY(MAX)) AS NVARCHAR(MAX)) like '%\\%'

and vrvcd > 123060

order by vrpid;

select cast(substring(uobindta,1,8000) as varchar(8000)) from PD920.F98950;

Performance Questionaire

 

Are they Hosted? If yes where -?

 

JDE Detail –

 Application Release –

Tool Release –

Bitness -

Batch Server – OS/RAM/CPU

Database Server and Version –

Database Server  - OS/RAM/CPU

 

 

JDE –

 

Since when the issue is happening ?

Any recent changes done at hardware level or JDE Software (New Promotion) or Third Party ?

Last Full Package build date ?

Run Report R9698711 and see missing index as per JDE Standard?

Does Job remain in Wait Status long enough before start Processing?

Is this Standard or Using custom?  Custom BSFN, RDA or Table etc ?

Can Job be run with AntiVirus turn off on Enterpriser and Database Server and See performance?

 

Does Payroll Job Run Faster if it run’s in single threaded Queue ?

Is there specific time when Job run faster and time when Job run slower ?

What parameter is the comparison of Job performance?

Does Same Job run faster in one environment vs other environment?

Does any other Job is slower

 

DBA -

Verify Database is performance ?

Check Index on Database?

Check Fragmentation on Database?

Check Database Backup timing and see if timing is conflict when the job is running?

 

Infra Team

Check Performance of System for last 10 days.  Provide Screen Shot for monitoring ?

Which Antivirus running and is JDE Folder excluded ?

JDE Tables

 CNC Tables

F986101 - Object Configuration Master

F98611 - Data Source Master

F98230 - OMW System Settings

F95921 - Role Relationships Table

F9654 - Deployment Locations Definition

F9651 - Machine Detail

F9650 - Machine Master

F00950 - Security Workbench Table

F00945 - Release Master

F00942T

F00941 - Environment Detail - One World

F00942 - Object Path Master File

F0094 - Library List Master File

F0092 -  Library Lists - User

ESU Table

F9670 - Software Update Master Table

F9671  - Software Update Detail Table

F9672 - Software Update Pathcode Information

F98881 - Specification Merge Logging File

F988810 - SpecMerge Tracking

Package Tables

F98220

F98221

F98222

F98223

F98224

Package Table

F9603

F96511

F98825

F98226

Understanding Kernel Refresh

 

Understanding Kernel Refresh

To optimize overall system workload into logical segments, JD Edwards EnterpriseOne assigns processing tasks to various kernel processes running on a JD Edwards EnterpriseOne Enterprise Server. These kernels use static and dynamic database connections at process initiation and maintains those connections to a database for the entire EnterpriseOne process life cycle. In case of any interruption to the database connection or connection sessions therein, the connection or session must be recovered or restarted. Understanding how static and dynamic EnterpriseOne database connections work and their impact on the JD Edwards system is important.

The JDBC interface of the EnterpriseOne HTML Server is a single-process connection to a database; on the other hand, multiple connections are made through the Enterprise Server kernel processes using JD Edwards EnterpriseOne CallObject kernels. The EnterpriseOne HTML Server depends on communication to the Enterprise Server Security kernel for authentication and other security process requests to function properly; thus loss of database connections on the Enterprise Server Security and Metadata kernel processes has a subsequent downstream effect on the EnterpriseOne HTML Server performance.

Kernels that are classified as static use a bootstrap login to establish the connection. This means that the login credentials are stored in and read from the jde.ini of the Enterprise Server. This is called the login environment. Unlike dynamic connections, a login to a static kernel is never logged out during the process lifetime. Again, this is because unlike dynamic connections, a static login environment is not subject to timeouts due to inactivity or logouts. Under normal conditions, these static kernels are only restarted when the Enterprise Server is restarted. Otherwise static kernels can only be restarted by manually killing the process and restarting it.

Among the key functions of a static kernel are database connections. If the connection to the database is temporarily lost for any reason such as network unavailability, the kernels have fault-tolerant logic to retry the connection for up to 75 seconds reusing the same connection. If the connection cannot be reestablished within 75 seconds, the process is failed. As previously mentioned, an entire static process can only be restarted by either restarting the Enterprise Server or by manually killing and restarting the process.

In order to avoid the situation where the database connection within a kernel process are in a failed state (timed out for more than 75 seconds) that is unknown to the system, functionality is added to Server Manager to refresh those database connections in static environments either periodically or on demand. This functionality is only available to an Admin user for Server Manager. When invoked, this function refreshes each static kernel for all database connections. The list of such static kernels may change from release to release, so it is not important that they be individually listed. Additionally, a static environment type, such as Security, may include multiple kernels of the same type. In such cases, this function will refresh each kernel in a static environment type.

It is important to note that the intent of a "refresh" is primarily to reestablish the database connections without resorting to a destructive "kill" action. As such, a refresh preserves the other logical states in the kernel and the kernel maintains the same internal functional state as it was prior to the refresh of the database connections.

One exception to the static kernel model is the Workflow kernel. This kernel can only free expired environments, that is, environments that have timed out. If a workflow environment is still active, it will not be forcibly freed by the refresh process.

Automatic Kernel Refresh

Note: The implementation of Automatic Kernel Refresh is only compatible with Oracle databases that are using multi node Real Time Application Cluster (RAC). This is because the process depends on the availability of a functioning node, which is not the case in a single node database in the event of a failure due to such factors are hardware or network issues. Multi node RAC environments are typically available for Oracle Autonomous Database (ADB) implementations.

In order to avoid disrupting normal processing, the JD Edwards kernel automatic kernel refresh logic only executes on an idle kernel process. If a kernel uses multiple threads, the logic will wait to refresh until all threads are idle. Basically a refresh involves a logout and a bootstrap login which reestablishes the database connections either using existing connections or establishing new connections; thus ensuring the connections are valid. This logout/login process does not kill a process or establish a new process - it reuses the existing process with reestablished database connections and returns the kernel to its prior state.

For implementation details, refer to the following section entitled: Using Automatic Kernel Refresh.

On-Demand Manual Kernel Refresh

You can use the Refresh Environments button to force a refresh for all static environments and CallObject kernels (which are dynamic kernels).

For static environments, the refresh will occur regardless of whether the kernel is idle. However, the refresh will wait until all threads of the kernel are complete. As with the automatic kernel refresh, the refresh does not kill a process or establish a new process - it reuses the existing process with reestablished database connections.

For CallObject kernels, these are dynamic kernels which are created by actual or programmatic user logins. Clicking the Refresh Environment button flags these kernels for recycling. In this case, recycling means the system will attempt to terminate a CallObject kernel gracefully, which means when all users of the CallObject kernel are either voluntarily logged out or forcibly logged out by an inactivity timeout (typically either 6 or 12 hours, for inactive or forced logouts, respectively). New CallObject kernels are created upon user login. This reestablishes the database connections for the kernel.

For example, in Production environments you might use the on-demand function if you are performing database patching during a planned maintenance window. In this case you would not be constrained by a short loss in system availability.

For implementation details, refer to the following section entitled: Using On-Demand Kernel Refresh.

https://docs.oracle.com/en/applications/jd-edwards/cross-product/9.2/eoism/understanding-kernel-refresh.html#u30154786

SQL Server and Database Collation

 

SELECT SERVERPROPERTY('Collation') AS 'Collation'

SELECT name, collation_name FROM sys.databases

The JDE Database Collation level should be Latin1_General_CI_AS_WS

msdb SQL_Latin1_General_CP1_CI_AS

DBA SQL_Latin1_General_CP1_CI_AS

JDE920 Latin1_General_CI_AS_WS

JDE_CRP Latin1_General_CI_AS_WS

JDE_DEVELOPMENT Latin1_General_CI_AS_WS

JDE_DV920 Latin1_General_CI_AS_WS

JDE_PRIST920 Latin1_General_CI_AS_WS

JDE_PS920 Latin1_General_CI_AS_WS

JDE_PY920 Latin1_General_CI_AS_WS

JDE_PD920 Latin1_General_CI_AS_WS

JDE_PRODUCTION Latin1_General_CI_AS_WS

JDE 64 Bit Full Package

 

In order to do first 64 Bit Full package for Fresh Install (when 32 bit Package not build), then add these specs to Base Full package. 

Add Specs to Full Package -
INSERT INTO DV920.F98710DV920FA SELECT * FROM DV920.F98710 WHERE THOBNM = 'F00942T';
INSERT INTO DV920.F98710DV920FA SELECT * FROM DV920.F98710 WHERE THOBNM = 'F98780R';
INSERT INTO DV920.F98710DV920FA SELECT * FROM DV920.F98710 WHERE THOBNM = 'F98780H';

INSERT INTO DV920.F98711DV920FA SELECT * FROM DV920.F98711 WHERE TDOBNM = 'F00942T';
INSERT INTO DV920.F98711DV920FA SELECT * FROM DV920.F98711 WHERE TDOBNM = 'F98780R';
INSERT INTO DV920.F98711DV920FA SELECT * FROM DV920.F98711 WHERE TDOBNM = 'F98780H';

INSERT INTO DV920.F98712DV920FA SELECT * FROM DV920.F98712 WHERE TPOBNM = 'F00942T';
INSERT INTO DV920.F98712DV920FA SELECT * FROM DV920.F98712 WHERE TPOBNM = 'F98780R';
INSERT INTO DV920.F98712DV920FA SELECT * FROM DV920.F98712 WHERE TPOBNM = 'F98780H';

INSERT INTO DV920.F98713DV920FA SELECT * FROM DV920.F98713 WHERE TLOBNM = 'F00942T';
INSERT INTO DV920.F98713DV920FA SELECT * FROM DV920.F98713 WHERE TLOBNM = 'F98780R';
INSERT INTO DV920.F98713DV920FA SELECT * FROM DV920.F98713 WHERE TLOBNM = 'F98780H';

Start Weblogic Admin Server, Node Manager and Server Manager Agent on Linux

 

Start Weblogic Admin Server, Node Manager and Server Manager Agent on Linux

1 Create system service files:

1.1 adminserver system service file

# vi /usr/lib/systemd/system/wls_adminserver.service

----------------------------------------------------

[Unit]

Description=WebLogic Adminserver Service

After=network.target 

[Service]

Type=simple

WorkingDirectory=/apps/oracle/middleware/user_projects/domains/E1_HTTP

ExecStart=/apps/oracle/middleware/user_projects/domains/E1_HTTP/bin/startWebLogic.sh

ExecStop=/apps/oracle/middleware/user_projects/domains/E1_HTTP/stopWebLogic.sh

User=oracle

Group=oinstall

[Install]

WantedBy=multi-user.target

1.2 nodemanager system service file

# vi /usr/lib/systemd/system/wls_nodemanager.service

------------------------------------------------------

[Unit]

Description=WebLogic NodeManager Service

After=network.target 

[Service]

Type=simple

WorkingDirectory=/apps/oracle/middleware/user_projects/domains/E1_HTTP

ExecStart=/apps/oracle/middleware/user_projects/domains/E1_HTTP/bin/startNodeManager.sh

ExecStop=/apps/oracle/middleware/user_projects/domains/E1_HTTP/bin/stopNodeManager.sh

User=oracle

Group=oinstall

[Install]

WantedBy=multi-user.target

1.3 JDE SM Agent system service file

# vi /usr/lib/systemd/system/wls_smagent.service

------------------------------------------------------

[Unit]

Description=Server Manager Agent Service

After=network.target

[Service]

Type=oneshot

WorkingDirectory=/apps/jde_home_agent/SCFHA

ExecStart=/apps/jde_home_agent/SCFHA/bin/startAgent

ExecStop=/apps/jde_home_agent/SCFHA/bin/stopAgent

RemainAfterExit=yes

User=oracle

Group=oinstall

[Install]

WantedBy=multi-user.target

3) Test the system service :

3.1 start system service

# systemctl start wls_adminserver.service

# systemctl start wls_nodemanager.service

# systemctl start wls_smagent.service

3.2 stop system service

# systemctl stop wls_adminserver.service

# systemctl stop wls_nodemanager.service

# systemctl stop wls_smagent.service

4) Set the service to start automatically at systm reboot :

# systemctl enable wls_adminserver.service

# systemctl enable wls_nodemanager.service

# systemctl enable wls_smagent.service

# systemctl list-unit-files|grep wls

JDE Julian and Calendar Date

JDE Excel Date Conversion

Julain to Gregorian Date

=DATE(YEAR("01/01/"&TEXT(1900+INT(A1/1000),0)),MONTH("01/01/"&TEXT(1900+INT(A1/1000),0)),DAY("01/01/"&TEXT(1900+INT(A1/1000),0)))+MOD(A1,1000)-1

Gregorian to Julian

=(YEAR(A1)-2000+100)*1000+A1-DATE(YEAR(A1),"01","01")+1

Linux Change Time Zone

 

1. View Time Zone 

Timedatectl

2. List Time Zone

timedatectl list-timezones

timedatectl list-timezones |grep Denver

timedatectl list-timezones | grep York

3. Set Time Zone

Based on timezone value need to set here is eg to set Denver or New York Time Zone

timedatectl set-timezone America/Denver

timedatectl set-timezone America/New_York

4.View Time Zone to verify timezone is set as required

Timedatectl

Reference - https://linuxize.com/post/how-to-set-or-change-timezone-in-linux/

JDE OMW SQL

 

To see List of Object 

1. List of Object Not-Checked Out and No- Token

SELECT FROM SY920.F98222 WHERE POOMWCHS='0' AND 'POOOMWOST='02' AND POOMWPOS1='0' AND POOMWPON1=0 AND POOMWPRJID='Project Name'

2. List of Object Not-Checked Out but have Token

SELECT FROM SY920.F98222 WHERE POOMWCHS='0' AND 'POOOMWOST='02' AND POOMWPOS1='1' AND POOMWPRJID='Project Name'

3. List of Object Checked Out and have Token

SELECT FROM SY920.F98222 WHERE POOMWCHS='1' AND 'POOOMWOST='03' AND POOMWPOS1='1' AND POOMWPRJID='Project Name'

4.  JDE OMW Token Release using SQL

UPDATE  SY920.F98222  SET POOMWPOS1='0',POOMWPON1=0 WHERE POOMWOST='02' AND POOMWPOS1='1'  AND POOMWPRJID LIKE '%2022%'

Print Weblogic Java GC Detail

 

Print GC Detail for Java  in Weblogic. Add this parameter in  server start section of Managed Server and restart service

Create Folder D:\Temp\GCLOG

 -Xloggc:D:\Temp\GCLOG\Prod_3278.log -verbose:gc -XX:+PrintGCDateStamps -XX:-PrintGCDetails

Restart Service and see GC logs in D:\Temp\GCLOG

To View Log you can see in Power Shell also using 

cd  D:\Temp\GCLOG

Get-Content -Path Prod_3278.log -Tail 50

Oracle Support page to Compare Apps & Tools release Net Changes

 

Oracle Support page to Compare Apps & Tools release Net Changes

 https://apexapps.oracle.com/pls/apex/f?p=103254:18:109497585364962::NO:RP,18:P_ID_18:208136276869697198410960926144257

How To Find OS Version On IBM i

 

To find the OS version of an IBM i (iSeries, AS/400), use the steps below:

1. Type the following on the command line: 
   DSPSFWRSC
2. Press 
   [F11]

The above commands will result in a screen similar to the one below:

Registering Fat Client DLL for 9.2.4.x

Registering Fat Client DLL for 9.2.4.x

--D:\E920\system\bin32\ Bitness is 32Registering files in
 D:\E920\system\bin32 ...
 D:\E920\system\bin32>C:\Windows\SysWOW64\regsvr32.exe /s .\ActivBPMInterface.dll
 D:\E920\system\bin32>C:\Windows\SysWOW64\regsvr32.exe /s .\ActivBPMXMLContent.dll
 D:\E920\system\bin32>C:\Windows\SysWOW64\regsvr32.exe /s .\activDocumentation.dll
 D:\E920\system\bin32>C:\Windows\SysWOW64\regsvr32.exe /s .\ActivDOM.dll
 D:\E920\system\bin32>C:\Windows\SysWOW64\regsvr32.exe /s .\activExplorer.dll
 D:\E920\system\bin32>C:\Windows\SysWOW64\regsvr32.exe /s .\ActivFindIt.dll
 D:\E920\system\bin32>C:\Windows\SysWOW64\regsvr32.exe /s .\activHeader.dll
 D:\E920\system\bin32>C:\Windows\SysWOW64\regsvr32.exe /s .\ActivMyActivEra.dll
 D:\E920\system\bin32>C:\Windows\SysWOW64\regsvr32.exe /s .\activProperties.dll
 D:\E920\system\bin32>C:\Windows\SysWOW64\regsvr32.exe /s .\activWebView.dll
 D:\E920\system\bin32>C:\Windows\SysWOW64\regsvr32.exe /s .\BPMLogger.dll
 D:\E920\system\bin32>C:\Windows\SysWOW64\regsvr32.exe /s .\CoMailMerge.dll
 D:\E920\system\bin32>C:\Windows\SysWOW64\regsvr32.exe /s .\dataitem.ocx
 D:\E920\system\bin32>C:\Windows\SysWOW64\regsvr32.exe /s .\DebuggerService.dll
 D:\E920\system\bin32>C:\Windows\SysWOW64\regsvr32.exe /s .\design.ocx
 D:\E920\system\bin32>C:\Windows\SysWOW64\regsvr32.exe /s .\E1Soap.dll
 D:\E920\system\bin32>C:\Windows\SysWOW64\regsvr32.exe /s .\EnvServer.dll
 D:\E920\system\bin32>C:\Windows\SysWOW64\regsvr32.exe /s .\EventClass.dll
 D:\E920\system\bin32>C:\Windows\SysWOW64\regsvr32.exe /s .\FDAAxHostMod.dll
 D:\E920\system\bin32>C:\Windows\SysWOW64\regsvr32.exe /s .\Jdboledb.dll
 D:\E920\system\bin32>C:\Windows\SysWOW64\regsvr32.exe /s .\JDEBPMSoap.dll
 D:\E920\system\bin32>C:\Windows\SysWOW64\regsvr32.exe /s .\JDEBPMSockets.dll
 D:\E920\system\bin32>C:\Windows\SysWOW64\regsvr32.exe /s .\jdectocx.ocx
 D:\E920\system\bin32>C:\Windows\SysWOW64\regsvr32.exe /s .\JDEMMC.dll
 D:\E920\system\bin32>C:\Windows\SysWOW64\regsvr32.exe /s .\Jdeocx.ocx
 D:\E920\system\bin32>C:\Windows\SysWOW64\regsvr32.exe /s .\Jdeowoda.dll
 D:\E920\system\bin32>C:\Windows\SysWOW64\regsvr32.exe /s .\jdesplash.dll
 D:\E920\system\bin32>C:\Windows\SysWOW64\regsvr32.exe /s .\JDETLBrowseMod.dll
 D:\E920\system\bin32>C:\Windows\SysWOW64\regsvr32.exe /s .\jdeuser.dll
 D:\E920\system\bin32>C:\Windows\SysWOW64\regsvr32.exe /s .\OneWorldInterfaceTx.dll
 D:\E920\system\bin32>C:\Windows\SysWOW64\regsvr32.exe /s .\RdaReportView.ocx
 D:\E920\system\bin32>C:\Windows\SysWOW64\regsvr32.exe /s .\TextCtrlMod.dll
 D:\E920\system\bin32>C:\Windows\SysWOW64\regsvr32.exe /s .\TLBrowseCtrlMod.dll
 D:\E920\system\bin32>C:\Windows\SysWOW64\regsvr32.exe /s .\WinUbeDbgService.dll

Fat Client JDE Folder permission missing

JDE Folder permission missing
In this example e1dbuser is a database user

"C:\Windows\SysWOW64\icacls.exe" "D:\E920" /grant "e1dbuser":F /t /c
"C:\Windows\SysWOW64\icacls.exe" "D:\Oracle" /grant "e1dbuser":F /t /c
"C:\Windows\SysWOW64\icacls.exe" "D:\Oracle32" /grant "e1dbuser":F /t /c

JDE Oracle ASM Tablespace

For ASM Database to create a Tablespace under Diskgroup use following command -

create tablespace dv920t datafile '+DATA' size 3072M autoextend on next 300M maxsize 5120M logging extent management local segment space management auto;
create tablespace dv920i datafile '+DATA' size 1536M autoextend on next 150M maxsize 3072M logging extent management local segment space management auto;
create tablespace testctli datafile '+DATA' size 1000M autoextend on next 100M maxsize 2000M logging extent management local segment space management auto;
create tablespace testctlt datafile '+DATA' size 1000M autoextend on next 100M maxsize 2000M logging extent management local segment space management auto;
create BIGFILE tablespace testdtai datafile '+DATA' size 1000M autoextend on next 100M maxsize 2000M logging extent management local segment space management auto;
create BIGFILE tablespace testdtat datafile '+DATA' size 1000M autoextend on next 100M maxsize 2000M logging extent management local segment space management auto;


create tablespace pd920t datafile '+DATA' size 3072M autoextend on next 300M maxsize 5120M logging extent management local segment space management auto;
create tablespace pd920i datafile '+DATA' size 1536M autoextend on next 150M maxsize 3072M logging extent management local segment space management auto;
create tablespace prodctli datafile '+DATA' size 1000M autoextend on next 100M maxsize 2000M logging extent management local segment space management auto;
create tablespace prodctlt datafile '+DATA' size 1000M autoextend on next 100M maxsize 2000M logging extent management local segment space management auto;
create BIGFILE tablespace proddtai datafile '+DATA' size 1000M autoextend on next 100M maxsize 2000M logging extent management local segment space management auto;
create BIGFILE tablespace proddtat datafile '+DATA' size 1000M autoextend on next 100M maxsize 2000M logging extent management local segment space management auto;

create tablespace py920t datafile '+DATA' size 3072M autoextend on next 300M maxsize 5120M logging extent management local segment space management auto;
create tablespace py920i datafile '+DATA' size 1536M autoextend on next 150M maxsize 3072M logging extent management local segment space management auto;
create tablespace crpctli datafile '+DATA' size 1000M autoextend on next 100M maxsize 2000M logging extent management local segment space management auto;
create tablespace crpctlt datafile '+DATA' size 1000M autoextend on next 100M maxsize 2000M logging extent management local segment space management auto;
create BIGFILE tablespace crpdtai datafile '+DATA' size 1000M autoextend on next 100M maxsize 2000M logging extent management local segment space management auto;
create BIGFILE tablespace crpdtat datafile '+DATA' size 1000M autoextend on next 100M maxsize 2000M logging extent management local segment space management auto;

create tablespace ps920t datafile '+DATA' size 3072M autoextend on next 300M maxsize 5120M logging extent management local segment space management auto;
create tablespace ps920i datafile '+DATA' size 1536M autoextend on next 150M maxsize 3072M logging extent management local segment space management auto;
create tablespace ps920ctli datafile '+DATA' size 1000M autoextend on next 100M maxsize 2000M logging extent management local segment space management auto;
create tablespace ps920ctlt datafile '+DATA' size 1000M autoextend on next 100M maxsize 2000M logging extent management local segment space management auto;
create BIGFILE tablespace ps920dtai datafile '+DATA' size 1000M autoextend on next 100M maxsize 2000M logging extent management local segment space management auto;
create BIGFILE tablespace ps920dtat datafile '+DATA' size 1000M autoextend on next 100M maxsize 2000M logging extent management local segment space management auto;


create tablespace sy920t datafile '+DATA' size 250M autoextend on next 25M maxsize 1000M logging extent management local segment space management auto;
create tablespace sy920i datafile '+DATA' size 100M autoextend on next 10M maxsize 1000M logging extent management local segment space management auto;
create tablespace svm920t datafile '+DATA' size 10M autoextend on next 1M maxsize 1000M logging extent management local segment space management auto;
create tablespace svm920i datafile '+DATA' size 10M autoextend on next 1M maxsize 1000M logging extent management local segment space management auto;
create tablespace ol920t datafile '+DATA' size 250M autoextend on next 5M maxsize 1000M logging extent management local  segment space management auto;
create tablespace ol920i datafile '+DATA' size 100M autoextend on next 5M maxsize 1000M logging extent management local  segment space management auto;
create tablespace dd920t datafile '+DATA' size 350M autoextend on next 10M maxsize 1000M logging extent management local  segment space management auto;
create tablespace dd920i datafile '+DATA' size 125M autoextend on next 5M maxsize 1000M logging extent management local segment space management auto;

When Installing JDE Set ORCL_set.sh as following value

Please set only ASM Disk Group to INDEX_PATH and TABLE_PATH.

export INDEX_PATH=DATA
export TABLE_PATH=DATA

Planner Backup

CREATE USER "JDEBACKUP" IDENTIFIED BY JD3BACKUP DEFAULT TABLESPACE "USERS" TEMPORARY TABLESPACE "TEMP" ACCOUNT UNLOCK ;
GRANT EXP_FULL_DATABASE TO JDEBACKUP;
GRANT IMP_FULL_DATABASE TO JDEBACKUP;
ALTER USER "JDEBACKUP" QUOTA UNLIMITED ON USERS;
CREATE OR REPLACE DIRECTORY BACKUP AS 'E:\Planner_DATABASE_BACKUP';
GRANT READ, WRITE ON DIRECTORY BACKUP TO JDEBACKUP;

cd\
E:
cd E1lOCAL_DATABASE_BACKUP
del *.* /q

cd\
E:
cd Oracle\E1Local\BIN

expdp JDEBACKUP/JD3BACKUP@E1Local DIRECTORY=BACKUP dumpfile=JDECTL920.dmp logfile=Exp_JDECTL920.log compression=none schemas=JDECTL920

expdp JDEBACKUP/JD3BACKUP@E1Local DIRECTORY=BACKUP dumpfile=JDEDATA920.dmp logfile=Exp_JDEDATA920.log compression=none schemas=JDEDATA920

expdp JDEBACKUP/JD3BACKUP@E1Local DIRECTORY=BACKUP dumpfile=JDEDD920.dmp logfile=Exp_JDEDD920.log compression=none schemas=JDEDD920

expdp JDEBACKUP/JD3BACKUP@E1Local DIRECTORY=BACKUP dumpfile=JDEOL920.dmp logfile=Exp_JDEOL920.log compression=none schemas=JDEOL920

expdp JDEBACKUP/JD3BACKUP@E1Local DIRECTORY=BACKUP dumpfile=JDEPLAN920.dmp logfile=Exp_JDEPLAN920.log compression=none schemas=JDEPLAN920

expdp JDEBACKUP/JD3BACKUP@E1Local DIRECTORY=BACKUP dumpfile=JDESY920.dmp logfile=Exp_JDESY920.log compression=none schemas=JDESY920

expdp JDEBACKUP/JD3BACKUP@E1Local DIRECTORY=BACKUP dumpfile=JDEVL920.dmp logfile=Exp_JDEVL920.log compression=none schemas=JDEVL920

expdp JDEBACKUP/JD3BACKUP@E1Local DIRECTORY=BACKUP dumpfile=SPEC_E920.dmp logfile=Exp_SPEC_E920.log compression=none schemas=SPEC_E920


Exit

Database Role JDEADMIN and JDEUSER

Starting with Application JDE 9.2 there comes 2 roles for Database JDEADMIN  and JDEUSER.

During upgrade these roles are not added to database which are migrated from older release.

Run these command


User JDE_DEVELOPMENT

Create role JDEADMIN
Create role JDEUSER
ALTER ROLE JDEADMIN ADD MEMBER JDE

exec sp_MSForEachTable 'GRANT ALTER,REFERENCES, SELECT, INSERT, DELETE, UPDATE ON ? TO [JDEADMIN]'
go

exec sp_MSForEachTable 'GRANT REFERENCES, SELECT, INSERT, DELETE, UPDATE ON ? TO [JDEUSER]'
go

Oracle Weblogic 12.2.1.3 Critical Patch Update (January 2019 OCPU)

Due to the increase in attack on Weblogic, Oracle is releasing Critical Patch Update every Quarter.

Below are the steps to Install Weblogic  Weblogic 12.2.1.3 January CPU patch set.  Remember if you already have the previous patch there are conflict sometimes, so you might have to uninstall the previous patchset before applying the latest one.

The Oracle Product Patch info is located at  https://www.oracle.com/technetwork/topics/security/alerts-086861.html

Download following Patch from  support.oracle.com

6880880 - Optach 13.9.4 Patch

29137924 - OUI Interim Patch

28710939 - Weblogic 12.2.1.3 Jan 2019 OCPU

1. Stop Weblogic Admin Server and All Managed Instance
2. Stop NodeManager Service
3. Stop Server Manager Agent
4. Make sure Task Manager no java process running
5. Unzip in a folder D:\Software\92\HTML\PatchSet using 7-zip (if it’s a linux system use command unzip )
6. Backup D:\Oracle\Middleware using 7-zip
7. open CMD  - Run As an administrator
8. set PATH=D:\OracleWLS\Middleware\Oracle_Home\OPatch;%PATH%
9. set PATH=D:\OracleWLS\Java\bin;%PATHH%
10. D:
11. cd D:\Software\92\HTML\PatchSet\6880880  (This is a directory in Step 5 to unzip folder)
12. java -jar opatch_generic.jar -J-Doracle.installer.oh_admin_acl=true -silent oracle_home=D:\OracleWLS\Middleware\Oracle_Home
13. cd ..
14. cd 29137924
15. opatch apply -oop
16. cd ..
17. cd 28710939
18. opatch apply -oop