Sie sind auf Seite 1von 11

Deletion Of Transaction Sequence

Work Instruction

Propriety and Confidential Rev 1.0 Page 1 of 11

Revision Revision date Description of change


(31-October-2017
1.0  Initial update
draft)

Prepared Approved Released


Process Leader Subject Matter Expert Process Champion BOS Regional Team

Alejandro Hernandez Mera (NA)


Andrea Aranha Alex Xavier

Signature (optional) Signature


Approval records maintained by BOS Team

1.0 Purpose
This work instruction describes the process for deletion of transaction history sequence when it is
nearing exhaustion and it has not been cleared by the ADU(Archive Delete Utility) jobs.

2.0 Scope
NA
This work instruction applies to MFG/PRO application.

3.0 Responsibility
The IT member working in the Support group is only responsible for the deleting the sequence and
coordinating with DBA support group.

Master files are stored electronically and are available to all team members.

Printed copies of the master files are for reference only.


Deletion Of Transaction Sequence

Work Instruction

Propriety and Confidential Rev 1.0 Page 2 of 11

4.0 Process
STEP 1:

First check the webpage report to see which of the plants transaction sequence is nearing exhaustion

http://a0300tc5p2.autoexpr.com/reports/SystemStatus/Sequence/tr_hist/

Below are few of the plant from the list.


Database Current Oldest Earliest Total Latest Forecast
Avail Record Seq Seqs Monthly Months
Seq Avail Date Avail Use To Crash
--------------------------------------------------------------------------

amfp607p 87685045 90333382 06/02/14 2648337 1573665 1.68


amfp278p 98300324 1599 10/10/01 1701274 630270 2.70
amfp204p 67906580 75279297 10/03/13 7372717 2338818 3.15
amfp339p 23818453 40004478 03/06/14 16186025 2515262 6.44
amfp056p 9419942 20001855 02/14/12 10581913 1555230 6.80
amfp787p 29999070 50002865 07/01/14 20003795 2288500 8.74
amfp919p 92120516 1 09/26/05 7879484 727731 10.83
amfp849p 35846338 60263160 08/18/14 24416822 2183208 11.18
amfp788p 22622649 45249868 10/05/15 22627219 1904741 11.88
amfp016p 88340175 1 08/15/01 11659825 945035 12.34
amfp043p 32441378 41137459 07/17/12 8696081 622524 13.97
amfpi09p 52146744 15105 05/31/15 47868360 2266832 21.12
amfp117p 81110837 1 03/15/02 18889163 796325 23.72
amfp090p 98939835 13653572 01/01/13 14713736 607868 24.21
amfp477p 53850709 77120387 01/07/10 23269678 837869 27.77
amfp356p 86526278 5322908 01/02/05 18796629 668093 28.13
amfp436p 97399883 10202942 10/01/02 12803058 390664 32.77
amfp664p 67123920 73292 07/06/12 32949371 911218 36.16
amfpi01p 37505207 23379 05/31/15 62518171 1383540 45.19
amfp881p 67925483 402 04/01/05 32074918 619843 51.75
amfp038p 67695385 44481 10/09/07 32349095 561819 57.58

Forecast months to crash denotes months left for the transaction sequence to exhaust.
For instance amfp607p has around 1 month of transaction sequences remaining.
Likewise amfp278p has around 2 months of transaction sequences remaining.

Master files are stored electronically and are available to all team members.

Printed copies of the master files are for reference only.


Deletion Of Transaction Sequence

Work Instruction

Propriety and Confidential Rev 1.0 Page 3 of 11

STEP 2:

Request DBA team to provide client script for the database for which you need to delete the old
transaction numbers.
So that all the deleted and archived transactions would be stored in a separate archive directory .

For instance for plant 607 below is the client script provided by DBA.

/global/mfgpro/usr/client_607.sh

And this would dump all the deleted tr_hist records to the archive path

/mfgdata/amfp607p/adu/aduarc

STEP 3:

Login into the server as provided by DBA with your credentials.

Master files are stored electronically and are available to all team members.

Printed copies of the master files are for reference only.


Deletion Of Transaction Sequence

Work Instruction

Propriety and Confidential Rev 1.0 Page 4 of 11

Enter the client script provided by DBA.

Enter the MFGPRO credentials

Master files are stored electronically and are available to all team members.

Printed copies of the master files are for reference only.


Deletion Of Transaction Sequence

Work Instruction

Propriety and Confidential Rev 1.0 Page 5 of 11

STEP 4:

Check if you are in the right database and it is pointing to the correct archive directory.

Master files are stored electronically and are available to all team members.

Printed copies of the master files are for reference only.


Deletion Of Transaction Sequence

Work Instruction

Propriety and Confidential Rev 1.0 Page 6 of 11

It shows the same archive directory as specified by DBA.

Master files are stored electronically and are available to all team members.

Printed copies of the master files are for reference only.


Deletion Of Transaction Sequence

Work Instruction

Propriety and Confidential Rev 1.0 Page 7 of 11

Press exit to return to the menu.

STEP 5:

Refer the webpage report again.

Database Current Oldest Earliest Total Latest Forecast


Avail Record Seq Seqs Monthly Months
Seq Avail Date Avail Use To Crash
--------------------------------------------------------------------------

amfp607p 87685045 90333382 06/02/14 2648337 1573665 1.68

It shows the oldest record available is “90333382” as of date 06/02/14.

Check for this record in 3.21.1

Master files are stored electronically and are available to all team members.

Printed copies of the master files are for reference only.


Deletion Of Transaction Sequence

Work Instruction

Propriety and Confidential Rev 1.0 Page 8 of 11

It is available.

STEP 6:

Go to menu 3.21.23

Master files are stored electronically and are available to all team members.

Printed copies of the master files are for reference only.


Deletion Of Transaction Sequence

Work Instruction

Propriety and Confidential Rev 1.0 Page 9 of 11

Enter the from date as seen in webpage report (Earliest Seq Date) and the to date as of one month date.
Delete the sequences per month.

Take output to any file name.

The output would be dumped to the path /mfgdata/<dbname>/adu/aduarc.

Request DBA team to check if the BI grows.

STEP 6:

After the completion of deletion please run the following query to delete the xtr_hist (shadow table) of
the orphan tr_hist records which are the just deleted tr_hist records in the TMS server or you can even
run the query in the Production server by raising a CN (Change notification) to DBA team and they would
run the following query.

Master files are stored electronically and are available to all team members.

Printed copies of the master files are for reference only.


Deletion Of Transaction Sequence

Work Instruction

Propriety and Confidential Rev 1.0 Page 10 of 11

FOR EACH xtr_hist :

    FIND FIRST tr_hist NO-LOCK WHERE tr_trnbr = xtr_trnbr NO-ERROR.

    IF NOT AVAILABLE tr_hist THEN DO:

        DELETE xtr_hist.

   END.

END.

5.0 Pre requisites


Need to obtain the client script from DBA team for deletion of transaction sequence.
This process needs to be followed only when the ADU(Archive delete utility) jobs fail to execute.

6.0 Records/Logs
Logged in the SharePoint.

https://connect.adient.com/sites/ITAMOMFGPrblmMngmnt/MFGPRO%20NA%20supprt
%20documents%20repository/Forms/AllItems.aspx?RootFolder=%2Fsites
%2FITAMOMFGPrblmMngmnt%2FMFGPRO%20NA%20supprt%20documents%20repository
%2FUser%20Guides&FolderCTID=0x012000891B74302637584983B524871C2ACC7B&View=
%7B7EED2F1A-A815-4F35-A02F-2CA331AD999F%7D

7.0 Reference
Forms for all documents to be delivered under “6.0 Records/Logs”.

Master files are stored electronically and are available to all team members.

Printed copies of the master files are for reference only.


Deletion Of Transaction Sequence

Work Instruction

Propriety and Confidential Rev 1.0 Page 11 of 11

Master files are stored electronically and are available to all team members.

Printed copies of the master files are for reference only.

Das könnte Ihnen auch gefallen