Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EPRS: added workaround for ORA-17056 #6593

Open
wants to merge 3 commits into
base: develop
Choose a base branch
from

Conversation

@gvasquezvargas gvasquezvargas requested a review from a team as a code owner March 7, 2025 16:02
@gvasquezvargas gvasquezvargas added the deploy Add this label to a PR and it will automatically be deployed to netlify label Mar 7, 2025
@gvasquezvargas gvasquezvargas marked this pull request as draft March 7, 2025 16:02
Copy link
Contributor

github-actions bot commented Mar 7, 2025

@github-actions github-actions bot temporarily deployed to pull request March 7, 2025 16:06 Inactive
@github-actions github-actions bot temporarily deployed to pull request March 10, 2025 09:39 Inactive
@gvasquezvargas gvasquezvargas marked this pull request as ready for review March 10, 2025 09:56
@gvasquezvargas gvasquezvargas force-pushed the eprs/oracle_ja16sjis_issue branch from 019666d to 444f281 Compare March 10, 2025 09:56
@github-actions github-actions bot temporarily deployed to pull request March 10, 2025 09:59 Inactive
1. Save the script and exit the editor. Restart the Publication Server to apply the changes.

1. Ensure the `ORA-17056` error message no longer appears and verify that the Publication Database was added successfully.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@gvasquezvargas Steps look fine.We can perhaps update the steps with correct numbering.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @RaviKumarEDB !
It is a markdown standard to use 1. only in numbered lists. They'll render correctly in the front end. If you check out the staging environment, you'll see the numbers are rendered correctly.
Screenshot 2025-03-10 at 16 19 12
The reason for this standard is that no matter how you later reorganize the steps (add one step, remove one step, etc.), you won't need to adapt the numbers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
deploy Add this label to a PR and it will automatically be deployed to netlify
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants