Hi Team,

This request has been assigned to DBA for running a query on application tables.

Could you please confirm if the expectation is really for DBA to execute this? As per usual controls, DBAs should not run application-level queries using privileged access on application-owned tables.

It looks like this may have been assigned to DBA a bit too quickly, so checking before we proceed.

Please confirm the application owner and the approved account/process to run this query.

Regards,
Nikhil

Posted By Nikhil09:21

0

Continue Reading

 

Title: Standard ID Remediation for Oracle LGTM Onboarding in Lower Environments

As a DBA / SRE working on Oracle LGTM onboarding,
I want to identify and remediate Standard ID related issues on lower environment Oracle hosts,
So that SRVAPD account deployment can complete successfully and LGTM onboarding can continue without repeated failures.

---

Background

As part of the LGTM onboarding activity, we are currently working on Oracle databases. After completing a few batches, we started seeing failures during the deployment of the SRVAPD account.

Initial investigation showed that the failures were not related to the LGTM onboarding flow itself, but were caused by underlying Standard ID issues on several lower environment servers.

The following issues were observed across different hosts:

• Standard ID was in a broken state.
• Standard ID details were missing from the expected source.
• Standard ID certificate was expired on some hosts.
• Pisa package related issues were also seen on a few servers.

Based on the investigation, we decided to segregate the issues by category, identify the ones with major weightage, and start remediation for the most common and high-impact cases first.

---

Scope of Work

• Identify lower environment Oracle hosts impacted by Standard ID issues.
• Segregate the failures based on the type of issue observed.
• Validate hosts where SRVAPD deployment failed due to Standard ID problems.
• Perform trial remediation on selected hosts.
• Develop a script to remediate Standard ID issues.
• Add required validations in the script to confirm the remediation is successful.
• Test the script on multiple hosts before wider rollout.
• Work with the automation team to deploy the script through Amelia.
• Use Amelia automation to remediate lower environment hosts.

---

Acceptance Criteria

• Affected hosts are identified and categorized based on the Standard ID issue.
• Major failure patterns are separated from one-off host-specific issues.
• Trial remediation is completed successfully on selected hosts.
• Remediation script is developed and tested.
• Script performs required pre-checks and post-checks.
• Script is deployed through Amelia automation.
• Lower environment hosts can be remediated using Amelia.
• SRVAPD account deployment is revalidated after remediation.
• Remediated hosts are ready to continue with LGTM onboarding.

---

Comments / Checklist

• [ ] Identified that SRVAPD account deployment started failing after a few LGTM onboarding batches.
• [ ] Investigated and confirmed that multiple lower environment servers had Standard ID in a broken state.
• [ ] Observed cases where Standard ID details were missing from the required source.
• [ ] Observed cases where Standard ID certificates were expired.
• [ ] Observed cases where Pisa package related issues were present.
• [ ] Segregated the issues based on failure category and impact.
• [ ] Performed trial remediation on various hosts to validate the fix.
• [ ] Developed a remediation script for Standard ID related issues.
• [ ] Tested the script on multiple hosts to ensure it works as expected.
• [ ] Added validations in the script to confirm Standard ID status before and after remediation.
• [ ] Worked with the automation team to deploy the script in Amelia.
• [ ] Plan to use Amelia automation for lower environment remediation.
• [ ] Revalidate SRVAPD deployment and LGTM onboarding after remediation.

Posted By Nikhil07:40

0

Continue Reading

 SET LINESIZE 300

SET PAGESIZE 50000

SET LONG 1000000

SET LONGCHUNKSIZE 1000000

SET TRIMSPOOL ON

SET WRAP ON

COLUMN hostname FORMAT A45

COLUMN script_result FORMAT A200

Posted By Nikhil07:34

0

Continue Reading

INSERT ALL

  INTO host_check_table (hostname) VALUES ('server01')

  INTO host_check_table (hostname) VALUES ('server02')

  INTO host_check_table (hostname) VALUES ('server03')

SELECT 1 FROM dual;

COMMIT;

UPDATE your_table_name

SET details = NULL

WHERE hostname = 'server02';

COMMIT;

SELECT hostname, details
FROM your_table_name
WHERE hostname = 'server02';

SET LONG 1000000

SET LONGCHUNKSIZE 1000000

SET LINESIZE 300

COLUMN script_result FORMAT A200

Posted By Nikhil07:13

0

Continue Reading

 

Hi Team,

We have raised the change for deploying the new policies, however this time the SDLC Release Checker has marked it as Not Compliant with the reason that no release is registered in SBC for the AA number.

In our previous similar changes, we do not recall receiving this specific task/validation requirement. Could you please help confirm if there has been any recent process change, or if any additional release registration is now required before this change can proceed?

Please also advise the next steps to make this change compliant.

Thanks,
Nikhil

Posted By Nikhil04:54

0

Continue Reading

 

Hi Sudhanshu,

Hope you are doing well.

As part of the Emerging DB discussions, we have biweekly sync calls with Microsoft. I will be taking up Anjali’s role for the time being, so could you please include me in the upcoming meeting invites, email conversations, and MOM/action item updates going forward?

This will help me stay aligned on the ongoing discussions, pending action items, and follow-ups.

Thanks,
Nikhil

Posted By Nikhil07:08

0

Continue Reading

 Policy, fix, compliance, and optimization items are progressing across AMR, Redis, Cosmos, DocumentDB, and Mongo DB vCore. Multiple policy updates are awaiting release, including TLS support, audit policy assignment, and audit-to-deny policy changes. Fixes related to TPAC access, ADO agent pool access, and Cosmos ICC evidence capture are in progress or testing. Optimization items to block expensive Redis Enterprise modules and support cost optimization through audit policy additions are also progressing.

Posted By Nikhil04:07

0

Continue Reading