Install, Upgrade, Clone, Patch - EBS (MOSC)

MOSC Banner

Resizing database prior to upgrade

edited Aug 20, 2021 9:54AM in Install, Upgrade, Clone, Patch - EBS (MOSC) 2 comments
I've run through a test upgrade where, prior to the upgrade I grew the transaction data and index tablespaces by a fair number of data files (30 or so) each sized 2000M.

Subsequently I'm investigating free space in the database and can see that in the majorityof data files only the first 400MB out of the 2000MB is used by segments. Has anyone else come across this and is this expected behaviour?

Also is it better to allocate many smalerl files or to let the file grow as large as it needs to be? (In a previous attempt at the upgrade I ended up with a datafile 35GB in size.

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

EBS LCM Tags

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center