Bw Administration

1) Earlier we use to monitor the datafile space,log space, cpu, the system resources, now we have surplus cpu capacity in the environment. 2) Lot of issues like the dataloading and deletion is no more now like in the past we face. 3) Functional people do monitoring on process chains if they have any issues they will let us know. 4) Withh in the CMC most of the systems are dual-stack and are used for only ABAP'S 5) BW uses to logon to Bw portal and we get a request to upload the report into the portal. 6) BI team will create a query and we need to link that query to the portal role,either we can upload a ABAP role or we have to do the mapping in the portal. 7) We don't create any worksets,iviews.Most of the time the query is directly published as per as the BI Person concern. 8) We have web dispatcher that calls the portal stack,users don't have place the link on the browser.We have a link on SSO portal just click on it takes directly to BW portal. 9) For monthly task, we have to clean the shadow tables and also see the missing indexes happen when they load data. 10) PSS tables used to are gone.When they because,that still we have to monitor

cause lot of problems but,after compression those issues do big data load or deletion we ask them to inform us cause lot of performance problems.Here, the log space tell them to add additional log file.

11) BI,we are on 7.01 with SP6. 12) No archiving is done,only standard basis objects those on ECC. 13) Regular issues on BW is like long running jobs,connectivity issues, transport issues,portal session open for long hours. 14) Hardware is upgraded,we are on the latest hardware as well as the OS and DB combination. 15) Regarding compression,we have to schedule a transports.We have to get the transports going for the tool and we have to pick the tables and compress it because we cannot compress the database wholly.