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

Response file used during installation #11

Closed
djdule opened this issue Apr 23, 2014 · 5 comments
Closed

Response file used during installation #11

djdule opened this issue Apr 23, 2014 · 5 comments

Comments

@djdule
Copy link

djdule commented Apr 23, 2014

Hi,

What would be best way to use non-standard response file during automated installation? I presume it would be modifying templates / db_install_...rsp.erb, but I just want to confirm if that is the case. Thanks.

@biemond
Copy link
Owner

biemond commented Apr 24, 2014

Hi,

indeed now you need to change templates / db_install_...rsp.erb
do you need to change a lot if so I can add support to use your own file.

@djdule
Copy link
Author

djdule commented Apr 24, 2014

Well, I do not know :) I am not DBA, but I got this question from DBA team. They are worried that default install of EE version will install bunch of unnecessary things that would require unneeded licenses, so they want to be able to control 100% installation process. I guess you would know better than me if this would be necessary feature.

@biemond
Copy link
Owner

biemond commented Apr 24, 2014

Ok

off course you can choose for standard one , SE or EE but other features like partitioning, statspack , active dataguard or pluggable databases you need to do it yourself . Don't think this is possible with a rsp template.

@djdule
Copy link
Author

djdule commented May 28, 2014

Hi,

Would it be possible to add support for custom response files ? It seems we would need them. Thanks a lotl.

@biemond
Copy link
Owner

biemond commented May 30, 2014

Hi,

can you provide me an working example so I can use that as a testcase.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants