Common Production Failures Encountered at BI Production Support ___________________________________________________Intellec t

Summary
This Knowledge brief helps BW Consultants And End Users as Quick reference guide, in solving Co ple! production "ssues, where in Ti e fra e is less# Contents$ "ssues Concerning the %pecific &roble and relevant solution in overco ing the proble in &roduction support environ ent# Co on &roduction 'ailures Encountered at BW &roduction %upport

(

u p# #################################################################################################################5 4#( Wh0 does the error occur2########################################################################################################################5 4#3 What happens when this error occur2 ######################################################################################################5 4#4 What can be the possible actions to be carried out2 ################################################################################5 1 6ob Cancellation in )74 %ource %0ste # #########################################################################################################8 1#( Wh0 does the error occur2########################################################################################################################8 1#3 What happens when this error occurs2 ####################################################################################################8 1#4 What can be the possible actions to be carried out2 ################################################################################8 5 "ncorrect data in &%A# ######################################################################################################################################8 5#( Wh0 the error does occur2########################################################################################################################8 5#3 What happens when this error occur2 ######################################################################################################8 5#4 What can be the possible actions to be carried out2 ################################################################################8 8 /. ./Cs in the %ource %0ste ##################################################1 (#( Wh0 does the error occur2########################################################################################################################1 (#3 What happens when this error occur2 ######################################################################################################1 (#4 What can be the possible actions to be carried out2 ################################################################################1 3 Ti e %ta p Error# ###########################################################################################################################################1 3#( Wh0 the error does occur2########################################################################################################################1 3#3 What happens when this error occur2 ######################################################################################################1 3#4 What can be the possible actions to be carried out2 ################################################################################1 4 Error occurred due to %hort .% Activation 'ailed######################################################################################################################################9 8#( Wh0 does the error occur2########################################################################################################################9 8#3 What happens when this error occur2 ######################################################################################################9 8#4 What can be the possible actions to be carried out2 ################################################################################9 9 Caller 9: is issing##########################################################################################################################################. -on Updated ". 9#3 What happens when this error occur2 ######################################################################################################.Common Production Failures Encountered at BI Production Support Table of Contents ( Transactional )'C Error*trfc+ . 9#( Wh0 does the error occur2########################################################################################################################. A<E)E=/TE was locked# #############################################################################.#3 What happens when this error occur2 ######################################################################################################. . 9#4 What can be the possible actions to be carried out2 ################################################################################.#4 What can be the possible actions to be carried out2 ################################################################################> > %A& )74 E!traction 6ob 'ailed# #######################################################################################################################> >#( What happens when this error occur2 ######################################################################################################> >#3 What can be the possible actions to be carried out2 ################################################################################> (: 'ile not found *%0ste Co and for file check failed+# ##############################################################################(: (:#( Wh0 the error does occur2####################################################################################################################(: (:#3 What happens when this error occur2 ##################################################################################################(: (:#4 What can be the possible actions to be carried out2 ############################################################################(: 3 . Attribute Change )un 'ailed . .#( Wh0 does the error occur2########################################################################################################################. .

Common Production Failures Encountered at BI Production Support (( Table space issue# #######################################################################################################################################(: ((#( Wh0 does the error occur2####################################################################################################################(: ((#3 What happens when this error occur2 ##################################################################################################(: ((#4 What can be the possible actions to be carried out2 ############################################################################(: 4 .

@ it will give the list of all %tuck <UWAs# The ?%tatus Te!t@ will appear )ed for the %tuck <UWAs which are not getting processed# And the ?Target %0ste @ for those <UWs should be ?W&(C<:(5@..ata%ource and the Transfer )ules are different# &#& $"at "appens '"en t"is error occur% • • The essage appears in the 6ob /verview in )%=/. it will give a selection screen with ?. ?User -a e@. it happens because the ti e sta p between the . thatAs the Bose BW &roduction s0ste # .ata=arts are changed in BW side# "n that case. from R($*# -t asks to login into the source s"stem# /nce logged in.tracte!# (ometimes -+*C are also stuck on R. occurs whenever LUW’s (Logical Unit of Work’s are not transferre! from the source s"stem to the !estination s"stem# 1#& $"at "appens '"en t"is error occur% • $essage a%%ears in the &ottom of the '(tatus) ta& in R($*# The error message woul! a%%ear like 'tRFC Error in (ource ("stem) or 'tRFC Error in +ata Warehouse) or sim%l" 'tRFC Error) !e%en!ing on the s"stem from where !ata is &eing e. those <UWAs which are identified properl0# %o that the0 get cleared. Ad inistrator Workbench# &#( $"at can be t"e possible actions to be carried out% • • Whenever we get such an error.9 and e!pand B". the error is as it is.Common Production Failures Encountered at BI Production Support 1 Transactional RFC Error(trfc) – Non Updated I !Cs in t"e Source System# 1#1 $"y does t"e error occur% • tRFC – Transact Remote Function Call Error.ata%ources are changed on the )74 side or the .ate@. an! check if the LUW’s get cleare! manuall" &" the s"stem# -f after 'cou%le) of Refresh. T)'C options# /n e!ecution with ?'.oc read0 to be transferred to application+# Keep the cursor on the error essage (pertainin) to I !C type RSR*ST only) and click &rocess tab *'.+ # This will push an0 stuck "doc on )74# =onitor the load for successful co pletion. and co plete the further loads if an0 in the &rocess Chain# • • • & Time Stamp Error# &#1 $"y t"e error does occur% • • The ?Ti e %ta p@ Error occurs when the Transfer )ules7%tructure *T)7T%+ are internall0 inactive in the s0ste # The0 can also occur whenever the . the Transfer )ules *T)+ is showing active status when checked# But the0 are actuall0 not./ si!e as there were no %rocessors availa&le to %rocess them# • 1#( $"at can be t"e possible actions to be carried out% • • • • • *nce this error is encountere!.ocs are stuck go to )74.o not e!ecute an0 other ". use Tcode B. we coul! tr" to Click a com%lete Refresh 'F0) in R($*./C which is not related have the ?Target %0ste @ as ?W&(C<:(5@# )ight Click and ?E!ecute@ or ?'8@ after selection. then follow the &elow ste%s 1uickl" as it ma" ha%%en that the loa! ma" fail with a short !um%# 2o to the menu Environment 34 Transact# RFC 34 -n the (ource ("stem. we first need to check the Transfer )ules *T)+ in the Ad inistrator Workbench# Check each rule if the0 are inactive# "f so then Activate the sa e# Cou need to first replicate the relevant data source. or in ?.atasources# ./C %tatus t0pe as 81 *".7s DE )eplicate . and the load on BW side gets co pleted successfull0# When "./C in inbound &rocessingA tab for ". b0 right click on the source s0ste of .ispla0 =essage@ option of the &rocess in the &C# Check the Transfer )ules in )%A(.

or in '+is%la" $essage) o%tion of the 9rocess in the 9C# • (#( $"at can be t"e possible actions to be carried out% • Usuall0 ?Ti e /ut@ Error results in a %hort .am%le sa" !ate fiel! is not in the format which is s%ecifie! in 8W.ata Warehouse 7 DE "n the %ource %0ste # • Alternativel0 we can check the Transaction %T33. then change the Q= status fro 0ellow to red# )eDtrigger the load and onitor the sa e# • =onitor the load for successful co pletion. Check whether the ti e out occurred after the e!traction or not# "t a0 happen that the data was e!tracted co pletel0 and then there was a short du p occurred# Then nothing needs to be done# • "n order to check whether the e!traction was done co pletel0 or not. ake sure we go through the co plete anal0sis of the short du p in detail before taking an0 actions# • "n case of Ti e /ut Error.u p DE "n the . and co plete the further loads if an0 in the &rocess Chain# ( Error occurred due to S"ort (#1 $"y does t"e error occur% • ump# • Whenever a 5o& fails with an error 'Time *ut) it means that the 6o& has &een sto%%e! !ue to some reason.uring such occasions. ICA<<F'U-CT"/-F%E-. we can check the option for ?</CK@# 'or activating onl0 those T)7T% which are "nactive.u p we go to the following. and 3 check bo!es# 'or activating onl0 those T)7T% which are set b0 so e lock.% activate the reJuest# • "f the data was not e!tracted co pletel0.Common Production Failures Encountered at BI Production Support • • • • .FE))/)I which occurred due to Ti e /ut in )74 side# • "n such cases following could be done# • "f the data was e!tracted co pletel0. for /. "nfo%ource -a e. Environ ent DE %hort .u p# "n order to check the %hort . an! the re1uest is still in "ellow state# 7n! as a result of the same it resulte! in Time *ut error# -t will lea! to a short !um% in the s"stem# Either in R. we ma" get a short !um% in the 8W s"stem or in the (ource ("stem R. then it ma" ha%%en that instea! of giving an error it ma" give a short !um%# Ever" time we trigger the loa!# (#& $"at "appens '"en t"is error occur% • We woul! get a Time *ut Error after the time which is s%ecifie! in the -nfo%ackage 34 Time *ut settings (which ma" or ma" not &e same for all -nfo9ackages # 8ut &" that time in &etween./# The message a%%ears in the 5o& *verview in R($*.etails@ tab in the 6ob /verview# Where in we can conclude whether the e!traction was done or not# "f it is a ?full load@ fro )74 then we can also check the no# of records in )%A4 in )74 and check if the sa e no of records are loaded in BW# • "n the short du p we a0 find that there is a )unti e Error. we can e!ecute the following ABA& )eport &rogra ?)%FT)A-%T)UFACT"GATEFA<<@# "t asks for %ource %0ste -a e. in the %ource %0ste 7 BW s0ste # And then choose the relevant option to check the short du p for the specific date and ti e# Here when we check the short du p. we can check the ?E!traction@ in the ?./ or in 8W# (hort !um% ma" also occur if there is some mismatch in the t"%e of incoming !ata# For e. we check for the option for ?/nl0 "nactive@# /nce e!ecuted it will activate the T)7T% again within that particular "nfo%ource even though the0 are alread0 active# -ow reDtrigger the "nfo&ackage again# =onitor the load for successful co pletion. and co plete the further loads if an0 in the &rocess Chain# 5 . then change the Q= status fro 0ellow to green# "f ?CUBE@ is getting loaded then create inde!es.

Incorrect data in /S0# . field and what in the data has the error# /nce we ake sure fro the E!traction.#( $"at can be t"e possible actions to be carried out% • • /nce confir ed with the error. which record.etails tab in the 6ob /verview that the data was co pletel0 e!tracted. but the sa -u eric# • The data load a0 be a 'lat 'ile load or it a0 be fro )74# =ostl0 it provided b0 the users a0 have incorrect for at# .ispla0 =essage@ option of the &rocess in the &C# • +#( $"at can be t"e possible actions to be carried out% • 'irstl0 we check the Kob status in the %ource %0ste # "t can be checked through Environ ent DE 6ob /verview DE "n the %ource %0ste # This a0 ask 0ou to login to the source s0ste )74# /nce logged in it will have so e preDentered selections.#1 $"y t"e error does occur% • "t a0 happen so e ti es that the inco ing data to BW is having so records have few incorrect entries# 'or e!a ple. then this error is encountered# This a0 be due to so e proble in the s0ste # %o e ti es it a0 also be due to so e other Kobs running in parallel which takes up all the &rocessors and the Kobs gets cancelled on )74 side# The error a0 or a0 not be resulted due to Ti e /ut# "t a0 happen that there would be so e s0ste hardware proble due to which these errors could occur# +#& $"at "appens '"en t"is error occurs% • The E!act Error essage is I6ob ter ination in source s0ste I# The e!act error essage a0 also differ.Common Production Failures Encountered at BI Production Support + . it a0 be ?The background Kob for data selection in the source s0ste has been ter inated@# Both the error essages ean the sa e# %o e ti es it a0 also give ?6ob Ter ination due to %0ste %hutdown@# The essage appears in the 6ob /verview in )%=/. has the erroneous data# Here we can also check the validit0 of the data with the previous successful load &%A data# 8 . we go ahead and check the ?. and co plete the further loads if an0 in the &rocess Chain# • • • • • . or in ?. we then check the status of the /. which will give u direct link to the &%A data .#& $"at "appens '"en t"is error occur% • The error essage will appear in the Kob overview and will guide 0ou what e!actl0 we need to do for the error occurred# e incorrect for at.etail@ tab of the 6ob /verview to check which )ecord. e!pected value was in lower case or if the data was e!pected in nu eric for . check if the0 are relevant. and then E!ecute# This will show 0ou the e!act status of the Kob# "t should show ?L@ under Canceled# The Kob na e generall0 starts with ?B")EQUF@ followed b0 s0ste generated nu ber# /nce we are confir that this error has occurred due to Kob cancellation.ob Cancellation in R-( Source System# +#1 $"y does t"e error occur% • • "f the Kob in )74 s0ste cancels due to so e reasons. which field. in the . we can actuall0 see here. or few upper case and data is in e was provided in Alpha a0 see that the 'lat 'ile The essage on the botto of the ?Header@ tab of the 6ob /verview in )%=/ will have ?&%A &flege@ written on it.%. Cube under the anage tab# The latest reJuest would be showing the Q= status as )ed# We need to reDtrigger the load again in such cases as the Kob is no longer active and it is cancelled# We reDtrigger the load fro BW# We first delete the )ed reJuest fro the anage tab of the "nfo&rovider and then reDtrigger the "nfo&ackage# =onitor the load for successful co pletion.

SACTREQ/0 S)1e t'1es 't 1a2 a!!)1 a(2 +'t. we then save it# /nce data in &%A is changed# We then again reconstruct the sa e reJuest fro the anage tab# Before we could reconstruct the reJuest.efault . or cause of an e!isting failed reJuest in the /.ata Target it red# /nce the data is activated Q= status turns into Mreen # • 'or successful activation of the failed reJuest. here do not change the Q= status as in =onitor its green but within the .atabase and gives an error /)AD :::8:# When activation of data takes place data is read in Active data table and then either "nserted or Updated# While doing this there are s0ste dead locks and /racle is unable to e!tend the e!tents# 1#& $"at "appens '"en t"is error occur% • The e!act error essage would be like ?Request REQU_3ZGI6LEA5MSAHIROA4QUTCOP8. it will show the record with error with traffic signal as ?)ed@# "n order to change data in &%A.ata it is fine if we have an e!isting failed reJuest# This happens as there are )oll back %eg ent errors in /racle . it needs to have Q= status as ?Mreen@# This will update the records again which are present in the reJuest =onitor the load for successful co pletion.%.ata%# .%.%# 'or =aster . 3C)11u('!at')( e**)* 4R5C !a667 )!!u**ed/ e**)*0 It 's a!tua662 due t) s)1e s2ste1 e**)*0 • The essage appears in the 6ob /verview in )%=/. which will open another window which will onl0 have the reJuest which is7are not activated# %elect the reJuest and then check the corresponding options on the botto # And then Click on ?%tart@ • This will set a background Kob for activation of the selected reJuest# • =onitor the load for successful co pletion. we can actuall0 see which data package failed during activation# • We can once again tr0 to anuall0 Activate the /. and co plete the further loads if an0 in the &rocess Chain# • • 1 ! S 0cti2ation Failed# 1#1 $"y does t"e error occur% • • • .ata &ackage specified in the "nfo&ackage# "n "nfo&ackage DE %cheduler DE .% activation it a0 fail giving status > error# /r due to lack of resources.uring data load in /.ata &ackage is reduced we again re trigger the load and reload the co plete data again# • Before starting the anual activation.'( RSO. onl0 then it will allow to change the data in &%A# /nce the change in the specific field entr0 in the record in &%A is done. status .Common Production Failures Encountered at BI Production Support • • When we check the data in the &%A. data a!"a#e $$$$%& '(!)**e!t +'t.ata Transfer# Here we can set the siNe of the . it is ver0 i portant to check if there was an e!isting failed ?)ed@ )eJuest# "f so ake sure 0ou delete the sa e before starting the anual activation# • This error is encountered at the first place and then rectified as at that point in ti e s0ste is not able to process the activation process via 1 different &arallel processes# This para eter is set in )%CU%TA3 transaction# <ater on the resources are free so the activation co pletes successfull0# 9 . or in ?. and co plete the further loads if an0 in the &rocess Chain# • "n case the above does not work out. "t a0 happen so eti es that the data gets e!tracted and loaded co pletel0. we check the siNe of the . we need to have the reJuest deleted fro =anage Tab of the "nfo&rovider first. but then at the ti e of the /.% Activation 'ailed@# 1#( $"at can be t"e possible actions to be carried out% • Whenever such error occurs the data is a0 or a0 not be co pletel0 loaded# "t is onl0 while activation it fails# Hence when we see the details of the Kob. click on the ?Activate@ button at the botto .ata &ackage# Here we need to ?reduce@ the a!i u siNe of the data package# %o that activation takes place successfull0# • /nce the siNe of the .ispla0 =essage@ option of the &rocess in the &C# • The e!act error essage is ?/.

ata &ackage and tr0 reloading.ata for the first ti e.% activation is taking place and at the sa e ti e there is another /. we can then go ahead and delete the red reJuest fro the anage tab in the "nfo&rovider# )eDtrigger the "nfo&ackage again# =onitor the load for successful co pletion. and s0ste tries to carr0 out HAC) for this new =.ata packet.ata &ackage siNe and load the "nfo &ackage# &rocessing so eti es is based on the siNe of . then it a0 happen that the s0ste a0 give the caller 9: error# o Whenever we are tr0ing to load the Transactional data which has aster data as one of the Characteristics and the value does not e!ist in =aster .% activation cause of no processes free.uring =aster .As and load data at the sa e ti e# /r we can load the =aster .ata "f the error is happening while /. then s0ste a0 classif0 the error as caller 9:# o "t is a s0ste error which can be seen under the ?%tatus@ tab in the 6ob over Giew# 3#& $"at "appens '"en t"is error occur% • • The e!act error essage is ?%0ste response ICaller 9:I is issing@# "t a0 happen that it a0 also log a short du p in the s0ste # "t can be checked at IEnviron ent DE %hort du p DE "n the .As for the records in the . then we can define processes in the T Code )%CU%TA3# "f error is occurring due to )ead7Write in /.ata is getting loaded for the first ti e then in that case we can reduce the . or in ?.ata Table of /.As# "f s0ste is unable to create %".% activation running parallel then in that case it a0 happen that the s0ste a0 classif0 the error as caller 9:# As there were no processes free for that /. load. or available for processing the /. .ata &ackage# Hence we can reduce the data package siNe and then reload the data again# We can also tr0 to split the data load into different data loads "f the error occurs in the cube load then we can tr0 to delete the inde!es of the cube and then reload the data again# "f we are tr0ing to load the Transactional and =aster .ata first and then load Transactional .ata WarehouseI# 3#( $"at can be t"e possible actions to be carried out% • "f the =aster .% and at the sa e ti e the data loading is also taking place to the sa e /.% activation.ata and also load the transactional data# o "f /.ispla0 =essage@ option of the &rocess in the &C# .%# 'or e!a ple if activation is happening for an /. so e ti es a lock is set b0 s0ste user A<E)E=/TE# This nor all0 occurs when HAC) is running for so e other =.ata table we get this error# %0ste can have difficultl0 in creating %".ata together and this error occurs then we can reduce the siNe of the . we can get this error essage# o "f the "nde!es of the cube are not deleted.Common Production Failures Encountered at BI Production Support 3 Caller 34 is missin)# 3#1 $"y does t"e error occur% • This error nor all0 occurs whenever BW encounters error and is not able to classif0 the # There could be ultiple reasons for the sa e o Whenever we are loading the =aster .% Activation# o "t also occurs whenever there is a )ead7Write occurring in the Active .# This is a scheduling proble # 5#& $"at "appens '"en t"is error occur% • The essage appears in the 6ob /verview in )%=/. as s0ste a0 be finding it difficult to create %".%.% then we need to ake changes in the schedule ti e of the data loading# /nce we are sure that the data has not been e!tracted co pletel0.As for the =aster .ata loads. it creates %". and co plete the further loads if an0 in the &rocess Chain# • • • • • • 5 0ttribute C"an)e Run Failed – 06ERE7!TE 'as loc8ed# 5#1 $"y does t"e error occur% • • .

ata# • • 9 S0/ R-( E:traction . e!traction Kobs get triggered in )74 via "nfo pack fro BW# Error a0 occur in the e!tract Kob or in the e!tract status Kob# 9#1 $"at "appens '"en t"is error occur% • • The e!act error essage nor all0 can be seen in the source s0ste where the e!traction occurs# "n BW the process for progra in the &C will fail# This &rocess is placed before the "nfo&ackage triggers. go to the TCode %=(3# This will give 0ou few options and couple of default entries# When we list the locks.uration*sec#+@ then it eans there is so e proble with the e!traction Kob# "t is not running.ata which is locked b0 user A<E)E=/TE# The lock which is set is because of load and HAC) ti ing which clashed# We first need to check )%A( DE Tools DE HAC). hence if the e!traction progra in )74 is still running or is not co plete. which will turn the ABA& process )E. trigger Attribute change run for this =aster . because it a0 happen that the e!tract Kob is finished but the e!tract status Kob has failed.elete the lock for the specific entr0 onl0 else it a0 happen that so e load which was running a0 fail. and is in dela0# "t a0 happen so eti es that there is no active Kob and there is a Kob which is in finished status with the current date7ti e# The e!tract Kob and the status Kob both needs to be checked.elete# %o that the e!isting lock is released# Care should be taken that we do not delete an active running Kob# &referable avoid this solution When HAC) finishes for the other =aster .ata. it will displa0 all the locks set# . and the e!tract status Kob both get co pleted# This is done so that on co pletion of these Kobs in )74. user. and click on . for the status of the Kob running in )74# Here it will show the e!act status of the running Kob# Enter the e!act Kob na e. the "nfo&ackage will not get triggered# Hence it beco es ver0 i portant to onitor such loads through )%&C rather than through )%=/# 9#& $"at can be t"e possible actions to be carried out% • • We login to the source s0ste and then check the T! Code %=49. then we e!ecute the '= ?O)%&CFABA&F'"-"%H@ with the specific variant and 6ob %tatus as ?)@ . or is failed.Common Production Failures Encountered at BI Production Support • The e!act error essage would be like. we anuall0 change the status of the E!tract &rogra &rocess in the &C in BW to green with the help of the '= ?O)%&CFABA&F'"-"%H@# E!ecute the '= with the correct na e of the &rogra process variant and the status ?'@# This will ake the &rocess green triggering the further loads# Here we need to check if there is no previous E!tract &rogra &rocess is running in the BW s0ste # Hence we need to check the &C logs in detail for an0 previous e!isting process pending# =onitor the &C to co plete the loads successfull0# "f in case we need to ake the ABA& &rocess within the &C to turn ?)E.# • • • • • > . which is Active with that na e# Cou a0 also find another Kob %cheduled for the ne!t load.ela0 *sec#+@ is increasing instead of ?. and choose the relevant options. as it will tell 0ou the e!act =aster . as a result of which it did not send success status to BW# But the e!traction was co plete# "n such cases. date. ?User A<E)E=/TE locked the load of characteristic :CU%T/=E)@# Here it is specificall0 for the :CU%T/=E) load# "t related to =aster . failure# Hence it is i portant that the e!tract Kob. or previous finished Kob# The active Kob is the one which is currentl0 running# Here if the Kob status for the ?.@ and retrigger the &C. Cancelled Kob if an0. then e!ecute# "t will show a list of the Kob.ata "nfo/bKect which is getting loaded# aster data for a0 be different 5#( $"at can be t"e possible actions to be carried out% • • Check the error essage co pletel0 and also check the long te!t of the error essage. due to the lock released# -ow we choose the appropriate lock which has caused the failure.ob Failed# There are certain Kobs which are triggered in )74 based upon events created there# These events are triggered fro %A& BW via ABA& &rogra attached in &rocess Chains# This e!tract Kob also triggers along with it a e!tract status Kob# The e!tract status Kob will send the status back to BW with success. where in we would get the list of "nfo/bKects on which HAC) is currentl0 running# /nce that is finished onl0 then.

.% *Which houses the an0 tables+ is full. particularl0 with respect to HAC) while the &rogra is doing realign ent of aggregates it needs lot of te porar0 table space Q&%ATE=&R# "f there is a large a ount of data to be processed and if /racle is not able to e!tend the table space it gives a du p# This nor all0 happens if there are an0 aggregates created on the sa e da0 or there is a large change in the inco ing =aster data 7 Hierarch0.. )elates to issues with table space# "t will give error as the /)A nu ber which asks to increase the table space# 11#( $"at can be t"e possible actions to be carried out% • • "n case the table space is full then we need to contact the Basis and accordingl0 ask for a increase in the siNe of the table space# The increase of the table space is done b0 changing so e para eters allocating ore space which is defined for individual tables# .% Activation stops and hence we a0 get failures# 11#& $"at "appens '"en t"is error occur% • The Error /)A D :(854 and /)A D :(8. so that large a ount of te porar0 e or0 is needed to perfor the realign ent# Also whenever the &%A&/. via the error essage in the &rocess# But we also need to send a ail. via the '=. and the corresponding actions to be taken# 11 Table space issue# 11#1 $"y does t"e error occur% • • • =an0 a ti es. else it beco es Mreen in &C# We need to check the script carefull0 for the above entioned e!it status# And then onl0 conclude that the file was reall0 not available# /nce confir ed that the file is not available we need to take appropriate actions# We need to identif0 the person who is responsible for 'T&ing the file on the Application server# A ail alread0 goes to the responsible person. regarding the sa e# The &rocess Chains which are having the s0ste co and &rocess in the .Common Production Failures Encountered at BI Production Support • This usuall0 needs to be done when the E!traction 6ob was cancelled in )74 due to so e reason P we have another Kob in )eleased state and the BW ABA& &rocess is in Cellow state# We can then ake the ABA& &rocess )E.( then failure i#e# &rocess beco es )ed. the data load 7 /. and then reDtrigger the &C# 14 File not found (System Command for file c"ec8 failed)# 14#1 $"y t"e error does occur% • • The s0ste co and process is placed in a &C before the infopackage &rocess# Hence it will check for the 'lat 'ile on the application server before the infopackage is triggered# This will ensure that when the load starts it has a 'lat 'ile to upload# "t a0 happen that the file is not available and the s0ste co and process fails# "n that case it will not trigger the "nfo&ackage# Hence it is ver0 i portant to onitor the &C through )%&C# 14#& $"at "appens '"en t"is error occur% • The error essage will turn the %0ste Co and &rocess in the &C ?)ed@ and the U-"L %cript which has failed will have a specific return code which deter ines that the script has failed# 14#( $"at can be t"e possible actions to be carried out% • • • • • Whenever the s0ste co and process fails it indicated that the file is not present# We right click on the &rocess and ?.ispla0 =essage@ we get to see the failed script# Here we need to check the return code#Here if e!it status is .